Systems and methods for supporting social productivity using a dashboard

ABSTRACT

Systems and methods provide a social productivity platform to create or modify documents and other data content objects using collaborative efforts, possibly where the efforts are received through a social networking service. The systems and methods can, for example, create, review and share documents, spreadsheets and presentations from any device, using any cloud storage provider. When teams of users collaboratively work on a document or other file, systems and methods connect each the team users to the document or file, and maintain a history buffer of comments, changes, or other events. The systems and methods enable a user to create, review, edit, or otherwise access content and capture information regarding changes implemented during individual or group-based editing to the content.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims the benefit of U.S. Provisional PatentApplication Ser. No. 61/834,381, filed Jun. 12, 2013 and entitled“System and Method for Supporting and Tracking Social Productivity,”U.S. Provisional Patent Application Ser. No. 61/843,920, filed Jul. 9,2013 and entitled “Systems and Methods for Supporting SocialProductivity,” and U.S. Provisional Patent Application Ser. No.61/881,398, filed Sep. 23, 2013 and entitled “Systems and Methods forSupporting Social Productivity,” which are hereby incorporated byreference herein.

BACKGROUND

1. Technical Field

The present invention(s) generally relate to server-based computing and,more particularly, relate to providing remote clients with collaborativefeatures, such as a workspace, that support social productivity.

2. Description of Related Art

In a server-based computing environment, hardware upgrades, applicationdeployment, technical support, and/or data storage can be provided byone or more terminal application servers. As such, use of server-basedcomputing to support multiple clients can reduce application costs andensure that applications are accessible by some or all of the supportedclients. Server-based computing also provides enhanced security andeliminates the need for patch through software upgrades to a pluralityof different clients. Traditionally, server-based computing has beenimplemented by way of remote desktop computing or remote applicationcomputing.

With remote desktop computing, one or more terminal application serversprovide one or more clients with access to a plurality of softwareapplications, and manage data transfers to each client through aseparate data communication line. Generally, users access the terminalserver through their end user devices (also known as “clients” or“client devices”) by authenticating into a network with a username andpassword, with an access card, based on biometric information, or by anyother authentication method. Upon establishing a remote desktopcomputing session, each client serves as a remote desktop displaycapable of displaying applications which are provided by the terminalapplication server. The remote desktop is created by and handled withinthe terminal application server based on applications installed on theterminal application server. The clients also allow users to input datathrough a mouse, keyboard, or the like, such that the users can interactwith the application provided by the terminal application server.

Unfortunately, traditional remote desktop computing is limited by theinability of the terminal server to provide access to disparateoperating systems (e.g., a traditional terminal server configured toprovide Microsoft® Windows® operating system is not capable of providingApple® OS X®-operating system), thereby requiring a user of remotedesktop computing to interface with different terminal servers foraccess to different operating systems. Traditional remote desktopcomputing is also limited by the inability of the terminal server toprovide the operating system with embedded access to a third-party,cloud-based storage (e.g., those provided by Dropbox, Box, or Google®Docs).

Additionally, traditional remote desktop computing is limited infeatures that enable teams of two or more users to collaboratively workon documents and other files, thereby hindering social-basedproductivity with respect to those documents and files. Various forms ofcommunication, hardware, and software fragmentation often exist amongusers who work remotely, and such fragmentation often hampers thecollaborative efforts of those users.

To illustrate, where a team of users is working collaboratively on oneor more documents, associated conversations between users is oftenfragmented as a result of team users using different means ofcommunication to facilitate such conversations (e.g., e-mail or chat) orteam users not including all team users in conversations (e.g., ane-mail thread relating to the collaboration includes some but not all ofthe team users). In another example, when individual team users utilizedifferent devices, software, or software services (e.g., one team userutilizes Google® Docs and another utilizes Microsoft® Word) duringcollaboratively efforts, such fragmentation can lead to documentcompatibility or document access issues. In addition, the fragmentationof communication, software, and hardware often results in usefulinformation (e.g., metadata) generated during collaborative efforts togo un-captured or to go unnoticed by other team users.

SUMMARY

Various systems and methods described herein relate to server-basedcomputing and, more particularly, providing remote clients withcollaborative features that support social productivity. Socialproductivity can include creating, reviewing, and sharing documents (orother types of data content objects) with a team of users workingcollaboratively on those documents. Various systems and methods cansupport social productivity by capturing, maintaining, and/or providinga history of comments, changes, communication, and other events withrespect to various types of data content objects being collaborativelyaccessed (e.g., worked upon) by groups of users. The systems and methodscan use the history to provide the group of users with various forms ofcontext regarding changes and other events in relation to a given datacontent object being collaboratively accessed. Additionally, based onthe history, various systems and methods can create and present anactivity stream for the given data content object, thereby providing forintelligent presentation of context regarding the given data contentobject as the given data content object is are being collaborativelyaccessed (e.g., collaboratively edited by a team of users).

According to some embodiments, systems and methods can detect an eventthat occurred with respect to a data content object (e.g., by receivingindication of the event occurring) as a result of an action (e.g., verb)performed on the data content object at a request of a first user (e.g.,actor). Subsequently, the systems and methods can capture contextualinformation relating to the event in a history buffer. Thereafter, thesystems and methods can provide a reference based on the contextualinformation, where the reference enables a second user to traverse to alocation in the data content object relating to the event. Examples ofevents can include changes implemented to content of the data contentobject, a user commenting regarding the data content object, a userreading content of the data content object, a user creating the datacontent object, a user saving the data content object, a user sharingthe data content object with another user, and communicating inconnection with a data content object. As used herein, comments caninclude text, audio, or video based comments, which can be associatedwith a data content object. The contextual information can includemetadata relating to, and possibly generated during, the event. Forexample, where the event is a change implemented to the data contentobject, the metadata may relate to the change implemented.

In some embodiments, the systems and methods can present the second userwith the reference in connection with notifying the second userregarding the event. Additionally, in some embodiments, the second usercan access the reference once presented.

In various embodiments, the systems and methods can present at leastsome of the contextual information in an activity stream describing oneor more events relating to the data content object. The systems andmethods can receive a request from the second user to traverse thereference to the location in the data content object relating to theevent. In response to the request from the second user, the systems andmethods can instruct an application (e.g., application capable ofprocessing a data-content-object) to traverse to the locationcorresponding to the reference. The application may be a virtualizedapplication instance executing in a virtual computing environment.

As used herein, “data content object” can refer to a file or can referto an object relating to a user, a group of users, a tag configured toassociate with another data content object, or a project. In someembodiments, the data content object can be a document file, such a wordprocessing file, a spreadsheet file, a presentation file, or apost-script document file. Additionally, in some embodiments, the datacontent object can be an electronic communication, such as an e-mail, atext-based message, multimedia message, or an instant chat message. Inaddition, in some embodiments, the data content object can be a file orother data structure that can include content relating to a profile,where the profile is associated with a person (e.g., user) or a group ofpeople (e.g., group of users). In various embodiments, a data contentobject can include content relating to a project and can be configuredto facilitate management of a project. Management of a project caninclude management of data content objects in connection with theproject, such as collecting or otherwise associating one or more datacontent objects with a project. Another example of managing a projectcan include associating one or more users with a project and controllingaccess to a data content object associated with a project. Further, insome embodiments, the data content object can be a tag configured to beassociated with another data content object. As user herein, a “tag” canbe one or more keywords that describe the data content object to whichit is associated. Examples of tags can include user-defined tags andhash tags, which may be compatible with one or more socialnetworking-based services (e.g., Facebook®, Twitter®, etc.). Thoseskilled in the art will appreciate that data content object can includetypes of data objects other than those listed or described herein.

As used herein, a “space” is an environment configured to provide accessto content of a data content object while providing contextualinformation relating to the data content object. The environment of aspace may be further configured to organize or exchange data content.For some embodiments, the configuration of a space can vary based on thetype of data content object being augmented. For example, each type ofdata content object can have an associated space (e.g., a “file space”augments file objects accessed therethrough, “people space” augmentspeople objects accessed therethrough, “group space” augments groupobjects accessed therethrough, “project space” augments project objectsaccessed therethrough, and “tag space” augments tag objects accessedtherethrough). Depending on the embodiment, a space may include agraphical user interface (GUI) that facilitates user interaction withthe space. Additionally, for some embodiments, when a space is focusedon (e.g., accessing) a data content object of a particular type (e.g.,people object), a space (e.g., file space) associated with a differenttype if data content object (e.g., file type) can be used to provideaccess to content of the data content object while providing contextualinformation relating to the data content object but as it relates to thedifferent type (e.g., from the perspective of the type of data contentobject to which the space relates).

For example, where a file space is being used to access a specificpeople object, the file space may provide contextual informationrelating to the specific people object but as it relates to fileobjects. In this example, such contextual information provided by thefile space may include providing a listing of file objects associatedwith the specific people object, or a listing of changes to file objectsperformed by the person associated with the specific people object. Inanother example, where a people space is being used to access a specificproject object, the people space may provide contextual informationrelating to the specific project object but as it relates to peopleobjects. In this second example, the contextual information provided bythe people space may include a listing of the people objects associatedwith the specific project object, or a listing of changes to objectsassociated with the specific project object according to the peopleobjects relating to such changes. Those skilled in the art willappreciate other combination of spaces and data-content-object types arepossible.

For example, a file space may capture content and information changes byone or more people on a data content object that is a file. In anotherexample, a people space may capture content and information changes witha given user. In another example, a project space may capture contentand information changes by groups of people on groups of file associatedwith a data content object that is a project.

As used herein, a “workspace” can refer to a general space (e.g., systemor user-created) that can hold spaces relating to data content objectsof one or more different types (e.g., file space, people space, groupspace, etc.), and that can agnostically augment different types of datacontent objects accessed through the workspace. Workspaces can beassociated with one or more users (e.g., through workspace sharing), andcan be associated such that the users can have varying levels of accessto data content objects accessible through the workspace. When accessinga workspace, a user can choose to access a data content objectassociated with the workspace, and the workspace may augment such accesswith contextual information historically gathered in relation to thedata content object. A workspace can include a dashboard configured toassist users in productively navigating issues and items of relevanceregarding data content objects access through the workspace, for exampleto create, present, publish or share content in data content objects(e.g., documents, spreadsheets and presentations).

For various embodiments, a user can choose to access one or more datacontent objects through the perspective of spaces associated withdifferent types of data content objects (e.g., file space, people space,group space, project space, tag space, etc.), and can choose to pivotbetween spaces according to the type of data content object beingaccessed. Additionally, a user can choose to access a collection ofdifferent types of data content objects through the perspective of asingle workspace, and can choose to pivot from a workspace to a specificspace by selecting a data content object associated with the space(e.g., selecting a data content object having a type associated with thespace). The user can also choose to pivot from a specific space to aworkspace.

Through the context-related features, spaces, such as workspaces, canfacilitate collaborative efforts, by two or more users, with respect toa data content object.

In some embodiments, the context (also referred to herein as “contextualinformation”) relating to a data content object can include an eventoccurring in relation to the data content object, such as atemporal-oriented, location-oriented, or relationship-oriented changefor the data content object. For example, an event can include anoperation relating to accessing content of the data content object or achange that results in content of the data content object. Examples ofaccessing can include a user reading, creating, modifying, removing,inserting, and moving content of the data content object. For instance,where the data content object is a word processing file, accessingcontent of the data content object can include opening and reading theword processing file and reading a section of the opened word processingfile. Other examples of events can include creating a data contentobject and removing a data content object. Examples of events can alsoinclude a user uploading a data content object (e.g., from clientcomputing device to a cloud storage service and in connection with aworkspace), a user downloading a data content object (e.g., from a cloudstorage service to a client computing device and in connection with aworkspace), a user sharing a data content object with another user(e.g., sharing access to some or all of the content of data contentobject with another), and associating or disassociating a data contentobject with respect to a tag, a project, or a workspace.

Where a plurality of events have occurred in relation to a data contentobject, the events can be generally referred to as “activity” of thedata content object, which can be provided or visually presented througha space as an activity stream or thread in connection the data contentobject. For some embodiments, such an activity stream or thread can bepresented as context by a space (e.g., workspace) used to access thedata content object.

According to some embodiments, systems and methods can detect a firstevent that occurred with respect to a first data content object as aresult of an action performed on the data content object at a request ofa first user. Subsequently, the systems and methods can determinewhether an attribute of the first event satisfies a criterion.Thereafter, the systems and methods provide a first card relating to theevent if the attribute is determined to satisfy the criterion (e.g.,meet or exceed a threshold condition), where the first card isconfigured to be presented to a second user.

As used herein, a “card” and “event card” can refer to a unit ofsummarized information regarding an event in association with a datacontent object. Depending on the embodiment, an event card may bepresented according to a bounded window of continuous activity relatingto the data content object. The window can be bounded by time, date,relevance to the percipient user (i.e., user perceiving the event card),or the type of data content object. The window can be bounded by one ormore criteria defined by the second user perceiving the event card.

In some embodiments, the systems and methods can present the first cardto the second user, where the first card can be presented in a dashboardconfigured to present a second card relating to a second event. Thesecond event may relate to a second data content object. The first cardcan comprise a secondary action configured to perform an operation withrespect to the first card at a request of the second user. Examples ofthe secondary actions can include: entering a comment in associationwith the first card; sharing the first card with another user, deferringpresentation of the first card, and assigning a task associated with theevent to another user (e.g., delegating).

In various embodiments, the systems and methods can determine thecriterion based on the second user. The criterion can define a frequencyof presentation of cards relating to the event, a restriction forpresenting cards based on event type, or an allowance for presentingcards based on event type. The criterion can be defined by the seconduser. Additionally, the criterion can be utilized to define relevancy ofevents to the second user.

According to some embodiments, systems and methods can associate a datacontent object with a workspace. Subsequently, the systems and methodscan detect an event that occurred with respect to the data contentobject as a result of an action performed on the data content object ata request of a first user associated with the workspace. Thereafter, thesystems and methods can inform a second user of the event, where thesecond user is associated with the workspace. Depending on theembodiment, the systems and methods can involve creating the datacontent object, or creating the workspace.

In some embodiments, the systems and methods can share the workspacewith the second user at the request of the first user. Additionally, insome embodiments, the systems and methods can share at least a portionof content in the data content object with another user at the requestof the first user.

In various embodiments, the systems and methods can delegate, at therequest of the first user, a task to another user in association with atleast a portion of content in the data content object. The systems andmethods can receive a response to the task from the other user. Thesystems and methods can to integrate the response into the portion ofcontent. The systems and methods can to inform the first user of theresponse.

In some embodiments, the systems and methods can provide a clientcomputing device with access to an application executing remotely fromthe client computing device (hereafter also referred to as “applicationaccess”), and providing application access in conjunction withsupporting social productivity features as described herein. Asdescribed herein, social productivity features can include providingcontext for content (hereafter also referred to as “content context”) ofdata content objects being accessed by the application executingremotely from the client computing device. The application may beremotely executed and provided such that the application accessed by auser has native access to a cloud-based storage, and data contentobjects (e.g., files) residing on the cloud-based storage. As usedherein, a “data-content-object processing application” can refer to anyapplication capable of processing or otherwise accessing a data contentobject.

According to some embodiments, systems and methods can determine events,performed on a first data content object, by a first user using adata-content-object processing application. The determination may bebased on information provided by the data-content-object processingapplication. The systems and methods can store event indicationsidentifying the events in a history buffer. Subsequently, the systemsand methods can select one or more particular event indications from thehistory buffer, where the one or more particular event indicationsidentify one or more particular events. Additionally, the systems andmethods can determine one or more other users authorized and designatedto receive a notification about the one or more particular events.Further, the systems and methods can determine whether the one or moreparticular event indications satisfy a one or more criteria (e.g.,threshold condition) permitting notification. Eventually, the systemsand methods can generate a data-content-object event notification to theone or more other users. The data-content-object event notificationgenerated may identify the one or more particular events performed onthe first data content object.

As described herein, the history buffer may be dedicated to the firstdata content object. Additionally, the first data content object and asecond data content object may belong to a workspace object, and thehistory buffer is dedicated to the workspace object. The first datacontent object may, for example, comprises a file or an object relatingto a user, a group of users, a tag configured to associate with anotherdata content object, or a project. The events may include, for example:reading, creating, modifying, removing, inserting, or moving content ofthe first data content object; creating, removing, uploading,downloading or sharing the first data content object; and associating ordisassociating the data content object to a workspace or a tag. Theevent indications may, for example, include user information, dateinformation, time information, or location information. Thedata-content-object event notification may provide a summary of changesperformed on the first data content object. The data-content-objectprocessing application may be a virtualized application instanceexecuting in a virtual computing environment.

In some embodiments, the step of determining one or more other usersauthorized and designated to receive a notification, about the one ormore particular events, may occur only after determining that the one ormore particular event indications satisfies the threshold conditionpermitting notification. Additionally, in some embodiments, the step ofgenerating a data-content-object event notification to the one or moreother users may occur only after determining that the one or moreparticular event indications satisfies the threshold conditionpermitting notification. Each of the one or more other users may set arespective threshold condition. The threshold condition may be one basedon, for example, a notification frequency, event type, an amount ofdetail requested, and/or the first data content object itself.

According to some embodiments, the systems and methods can await receiptof one or more data-content-object share indications that indicate thatone or more data content objects has been shared by a user at a secondclient device with a user of the first client device. The one or moredata content objects may be stored in one or more data stores. Inresponse to receiving a particular data-content-object share indicationthat a particular data content object has been shared, the systems andmethods may generate a particular share notification. The systems andmethods can further await receipt of one or more data-content-objectedit indications that identify one or more edits to the particular datacontent object. In response to receiving a particulardata-content-object edit indication that identifies one or moreparticular edits to the particular data content object, the systems andmethods may generate a particular edit notification. The systems andmethods can also await receipt of one or more task indications thatrequest the user of the first client device to perform one or moretasks. In response to receiving a particular task indication, thesystems and methods may generate a particular task notification.Additionally, the systems and methods can also await receipt of one ormore message indications that include one or more messages from thesecond user at the second client device. in response to receiving aparticular message indication, the systems and methods can generate aparticular message notification.

Eventually, the systems and methods may present a dashboard on the firstclient device. The dashboard may provide a portal to the particular datacontent object. The dashboard may, for example, include a first sectionfor displaying share notifications including the particular sharenotification, a second section different that the first section fordisplaying edit notifications including the particular editnotification, a third section different than the other sections (e.g.,first and second sections) for displaying task notifications includingthe particular task notification, and/or a fourth section different thanthe other sections (e.g., first and second sections) for displayingmessage notifications including the particular message notification. Thedashboard may also include a count section, the count section being fordisplaying a count of the number of notifications in each section.Depending on the embodiment, the dashboard may present the notificationsusing cards, with each card reporting at least one notification. Eachdashboard may enable filtering the notifications according to one ormore conditions.

In some embodiments, the one or more data stores may include cloudstorage. Additionally, the one or more edits to the particular datacontent object may be those performed by the user at the second clientdevice. The dashboard may provide a link to the particular data contentobject.

According to certain embodiments, a computer program product comprisingcomputer instruction codes configured to cause the computer system toperform the operations described herein. Additionally, particularembodiments may be implemented using a digital device as describedherein, such a computer system.

Other features and aspects of various embodiments will become apparentfrom the following detailed description, taken in conjunction with theaccompanying drawings, which illustrate, by way of example, the featuresof such embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments are described in detail with reference to thefollowing figures. The drawings are provided for purposes ofillustration only and merely depict some embodiments. These drawingsshall not be considered limiting of the breadth, scope, or applicabilityof embodiments.

FIG. 1 is a block diagram illustrating an example environment utilizingan example system for supporting social productivity in accordance withvarious embodiments.

FIG. 2A is a block diagram illustrating an example environment utilizingan example system for supporting social productivity in accordance withvarious embodiments.

FIG. 2B is a block diagram illustrating an example storage module thatis part of an example system for supporting social productivity inaccordance with various embodiments.

FIG. 3 is a block diagram illustrating an example environment utilizingan example system for supporting social productivity in accordance withvarious embodiments.

FIG. 4 is a block diagram illustrating an example context module that ispart of an example system for supporting social productivity inaccordance with various embodiments.

FIG. 5 is a block diagram illustrating an example workspace module thatis part of an example system for supporting social productivity inaccordance with various embodiments.

FIG. 6 is a block diagram illustrating an example dashboard module thatis part of an example system for supporting social productivity inaccordance with various embodiments.

FIG. 7 is a flowchart illustrating an example method for providingcontext capture that supports social productivity in accordance withvarious embodiments.

FIG. 8 is a flowchart illustrating an example method for a workspacethat supports social productivity in accordance with variousembodiments.

FIG. 9 is a flowchart illustrating an example method for a dashboardthat supports social productivity in accordance with variousembodiments.

FIG. 10 is a flowchart illustrating an example method for capturingcontext information, from a virtualized application, that supportssocial productivity in accordance with various embodiments.

FIG. 11 is a flowchart illustrating an example method for traversing toa position related to an event in accordance with various embodiments.

FIG. 12 is a screenshot of an example interface for accessing a datacontent object that is a file and presenting context in accordance withvarious embodiments.

FIG. 13 is a screenshot of an example interface for accessing a datacontent object that is a file and presenting context in accordance withvarious embodiments.

FIG. 14 is a screenshot of an example interface for accessing a datacontent object that is a file and for delegating portions of content ofdata content object in accordance with various embodiments.

FIG. 15 provides screenshots of example interfaces for accessing sharedportions of content of a data content object file that is a file inaccordance with various embodiments.

FIG. 16 is a screenshot of an example interface for accessing a space inassociation with a data content object that is a file in accordance withvarious embodiments.

FIG. 17 is a screenshot of an example interface for accessing a listingof workspaces in accordance with various embodiments.

FIG. 18 provides screenshots of example interfaces for creating andsharing workspaces in accordance with various embodiments.

FIG. 19 is a screenshot of an example interface for accessing aworkspace in accordance with various embodiments.

FIG. 20 is a screenshot of an example dashboard interface in accordancewith various embodiments.

FIG. 21 provides screenshots of example event cards for an exampledashboard in accordance with various embodiments.

FIG. 22 is a block diagram illustrating an exemplary digital device thatcan be utilized in the implementation of various embodiments.

DETAILED DESCRIPTION

Various systems and methods described herein relate to server-basedcomputing and, more particularly, providing remote clients withcollaborative features that support social productivity. In particular,various embodiments provide for systems and methods that can providesocial productivity platform that can create or modify documents andother types of data content objects using collaborative efforts,possibly where the efforts are received through a social networkingservice. The systems and methods can, for example, create, review andshare documents, spreadsheets and presentations from any device, usingany cloud storage provider. When teams of users are collaborativelyworking on a document or other file, various systems and methods canconnect each of the team users to the document or file, and maintain abuffer of comments, changes, or other events. For some embodiments, thesystems and methods can maintain a separate history buffer for everydata content object, or a separate history buffer for a type of datacontent object.

In some embodiments, the systems and methods can enable a user tocreate, review, edit, or otherwise access content of data contentobjects (e.g., documents) and capture information regarding changesimplemented during individual or group-based editing to the content. Indoing so, various embodiments can capture contextual information thatcan be provided as a data content object is being accessed. In someembodiments, the contextual information can facilitate creation andpresentation of an activity stream in connection with a data contentobject. Contextual information regarding a data content object caninclude metadata relating to an operation performed on content of thedata content object. Operations can include: reading, writing,modifying, creating, removing, inserting, or moving content of the datacontent object; creating, removing, uploading, downloading of the datacontent object; sharing the data content object with another; andassociating or disassociating the data content object with a workspaceor another data content object (e.g., tag).

For various embodiments, the systems and methods can implement acentralized hub for data content object productivity, which mayfacilitate faster workflow and/or easier management of viewing andauthoring data content object, particularly from a mobile digitaldevice. For some embodiments, the systems and methods can be implementedas a layer between a client and a content authoring system configured tohandle various data content objects. Additionally, in some embodiments,the systems and methods can be implemented to interact with, or be apart of, a social networking service.

The systems and methods can be configured to interact with various typesof data content object, which include files, projects, people, tags, orlocation. As described herein, each type of data content object may beassociated with a space configured to capture content and informationchanges with respect to a data content object of the type. For example,a file space may capture content and information changes by one or morepeople on a data content object that is a file. In another example, apeople space may capture content and information changes with a givenuser. In another example, a project space may capture content andinformation changes by groups of people on groups of file associatedwith a data content object that is a project.

As described herein, a workspace may be a general space that can holdall other types of spaces (e.g., file space, people space, group space,etc.), that can be associated with one or more data content objects ofone or more types, and that can agnostically augment different types ofdata content objects accessed through the workspace. Workspaces can beassociated with one or more users (e.g., through workspace sharing), andcan be associated such that the users can have varying levels of accessto data content objects accessible through the workspace. A workspacecan include a dashboard configured to assist users in productivelynavigating issues and items of relevance regarding data content objectsaccess through the workspace, for example to create, present, publish orshare content in data content objects (e.g., documents, spreadsheets andpresentations). The relevance may be determined based on variousfactors, including the preferences of the user perceiving the dashboard(the percipient user) and the history of activity by the user perceivingthe dashboard, and the like. The relevance and/or preferences for theuser may be implemented by way of one or more criteria used by thedashboard when displaying event cards to the user.

In accordance with various embodiments, the systems and methodsdescribed herein provide a client computing device with access to anapplication executing remotely from the client computing device, andprovide context for content of data content objects being accessed bythe application executing remotely from the client computing device. Thecontent context provided may be separate, distinct from, or in additionto any context provided by the application executing remotely from thecomputing device. In this way, various embodiments can agnosticallyprovide contextual information regarding the access of data contentobjects regardless of the method of access data content objects.

According to some embodiments, the systems and methods provide aplatform between the client computing device and an application serverthat is executing the application on behalf of the client computingdevice. In addition to providing the client computing device with accessto the application remotely executing on the application server, theplatform may maintain and provide contextual information regarding theapplication's access of a data content objects—contextual informationthat otherwise may not be maintained or provided by the application.

Additionally, the application may be accessing content of data contentobjects (e.g., one or more files) residing on a cloud-based storage(e.g., provided by a third-party cloud-based storage service). For somesystems and methods, the application may be remotely executed andprovided such that the application accessed by a user has native accessto a cloud-based storage, and data content objects (e.g., files)residing on the cloud-based storage. In this way, various embodimentsmay provide a user on a client computing device with universal andagnostic access to applications that would otherwise be non-operable onthe client computing device, and permit such applications with universaland/or agnostic access to cloud-based storage services that areotherwise disconnected from, disparate from, or incompatible with theaccessed applications. Additionally, some embodiments may permit anoriginal application, natively operating on the client computing devicebut incompatible with a particular data content object (e.g., an e-mailapplication operating on the client computing device attempting to opena spreadsheet file otherwise incompatible with e-mail application), toupload the data content object to a cloud-based storage service, andenable a remotely executed application, provided in accordance with theembodiments, compatible with the data content object, and capable ofaccessing the cloud-based storage service, to open the data contentobject on behalf of the original application.

Those skilled in the art will appreciate accessing a file, as understoodherein, can include, for example, creating, deleting, viewing (e.g.,opening), or modifying the file and any of content contained therein.Additionally, as understood herein, those skilled in the art willappreciate that accessing an application can include, for instance,starting, stopping, using, or otherwise controlling operation of theapplication, and may further include modifying the availability of theapplication (e.g., adding or deleting availability of the application).Any mention of a cloud-based service (e.g., storage, application) withinthis description will be understood to include, without limitation,services provided by private clouds, public clouds, and hybrid clouds.

FIG. 1 is a block diagram illustrating an exemplary environment 100utilizing an exemplary system for supporting social productivity inaccordance with various embodiments. As shown in FIG. 1, the exemplaryenvironment 100 comprises a client 102, an application service provider(ASP) system 104, a database server 106, a file server 108, acloud-based service server 110, and a messaging service server 112, eachof which may be communicatively coupled with each other usingcommunication connections 114. According to some embodiments, theapplication service provider (ASP) system 104 may be configured toprovide the client 102 with application access in conjunction withsupport for social productivity as described herein. The support forsocial productivity may include, for example, features relating tocapturing context for data content objects, dashboards, spaces, andworkspaces. In some embodiments, the communication connections 114 maybe implemented or facilitated using one or more local or wide-areacommunications networks, such as the Internet, WiFi networks, WiMaxnetworks, and the like. Depending on the embodiments, some or all of thecommunication connections 114 may utilize encryption (e.g., SecureSockets Layer [SSL]) to secure information being transferred over theconnections 114 between the various entities shown in the exemplaryenvironment 100.

Each of the client 102, the ASP system 104, the database server 106, thefile server 108, the cloud-based service server 110, and the messagingservice server 112 may be implemented using one or more digital devices,which may be similar to the digital devices discussed later with respectto FIG. 22. For instance, client 102 may be any form of computing devicecapable of receiving user input (e.g., configured for user interaction),capable of displaying a client user interface (e.g., through which anapplication can be viewed or controlled), and capable of communicatingwith the ASP system 104 over one or more of the communicationconnection(s) 114. Such computing devices may include a mobile phone, atablet computing device, a laptop, a desktop computer, personal digitalassistant, a portable gaming unit, a wired gaming unit, a thin client, aset-top box, a portable multi-media player, or any other type of networkaccessible user device known to those of skill in the art. Further, oneor more of the ASP system 104, the database server 106, the file server108, the cloud-based service server 110, or the messaging service server112 may comprise of one or more servers, which may be operating on orimplemented using one or more cloud-based services (e.g.,System-as-a-Service [SaaS], Platform-as-a-Service [PaaS], orInfrastructure-as-a-Service [IaaS]).

The client 102 may be configured to communicatively connect with the ASPsystem 104 and be provided with access to an application and socialproductivity features through the ASP system 104. According to someembodiments, the ASP system 104 can maintain application sessions,gather metadata and other contextual information regarding data contentobjects accessed through the ASP system 104, and connect storageservices (e.g., provided by third-party cloud-based storage providers)with application services (e.g., provided by application servers).

The application being provided through the ASP system 104 may beexecuted remotely from the client 102, and/or may be executed on orunder the control of the ASP system 104. The ASP system 104 may beexecuting or controlling the execution of the application on behalf ofthe client 102 and, as such, may facilitate access (e.g., video, audio,and data access) and user interaction between the executing applicationand the client 102.

The ASP system 104 may also be configured to provide the client 102 withfeatures supporting social productivity as the client 102 accesses theapplication executing on behalf of the client 102. For example, the ASPsystem 104 may capture contextual information regarding data contentobject as such data content objects are accessed by the client 102through the ASP system 104, possibly using the application executing onbehalf of the client 102. The ASP system 104 may provide the client 102with a workspace, or other type space, through which the client 102 canaccess different data content objects while being providing contextualinformation regarding such objects. The ASP system 104 may provide theclient 102 with a dashboard that assists a user at the client 102 inreviewing events associated with data content objects that areaccessible to the client 102 through the ASP system 104 (e.g., through aspace, such as a workspace) and that are relevant to the user. Asdescribed herein, a user may navigate from the dashboard to a locationin the content of a data content object that relates to an eventregarding the data content object (e.g., a change in content or someonereading the content).

The ASP system 104 may further execute or control the execution of theapplication such that the application has native access (e.g.,in-application access) to one or more files or other data contentobjects residing on a cloud-based storage external to the client 102 andthe ASP system 104. In various embodiments, such a cloud-based storageservice may be provided by a third-party cloud-based storage service(e.g., Dropbox or Box), which is separate and distinct from the ASPsystem 104. Execution or execution control of the application mayfurther provide the client 102 with the application having native accessto databases (e.g., served by the database server 106) or to fileservers (e.g., the file server 108) that are separate and distinct fromthe ASP system 104.

By executing or controlling execution of the application such that ithas access to data separate and distinct from the execution of theapplication, the ASP system 104 may provide the client 102 with remoteaccess to the application that might otherwise not be operable on theclient 102 and that has access to data storage provided by third-partyservices. In some embodiments, this may also allow an operator of theASP system 104 to provide user with applications as a remotelyaccessible service (e.g., for rent) without the need for maintaininglong-term storage data on the ASP system 104 (e.g., user data opened inthe applications are provided by a storage system and that is distinctfrom the ASP system 104; the storage system may be maintained by theuser or a third-party on behalf of the user).

This may be useful, for example, when the application is incompatiblewith the operating system running on the client 102, when the client 102lacks the requisite resources to locally execute the application (e.g.,lack of memory space or processor performance), or when the client 102lacks sufficient resources to properly execute the application locally.

In some instances, the cloud-based storage services accessed by variousembodiments may provide additional cloud-based services in conjunctionwith the storage services. These additional cloud-based services mayinclude such web-application services relating to data content objects,such as word processing documents, spreadsheet documents, presentationdocuments, and the like. An example of such a cloud-based service isGoogle® Docs. Various embodiments may utilize web-application services,in conjunction with or in place of virtualized applications, whenaccessing various data content objects (e.g., files) through the ASPsystem 104. For example, where a spreadsheet file being accessed throughthe ASP system 104 is stored on a Dropbox, the ASP system 104 may accessthe spreadsheet file from Dropbox and use a Google® Docs web applicationto open the spreadsheet file for viewing and/or modification purposes.

With various social productivity features provided by the ASP system104, such as spaces (e.g., workspaces), the ASP system 104 can permitone or more users to uniformly and collaboratively access to datacontent objects, which may be stored on one or more of the databaseserver 106, the file server 108, and the cloud-based service server 110providing a cloud-based storage service. For example, one or more datacontent objects can be accessed by the client 102, through the ASPsystem 104, from storage external to the client 102 and the ASP system104. As the one or more data content objects are accessed, the ASPsystem 104 can capture and collect contextual information regarding theaccess of the data content object. The contextual information capturedfor a data content object can include information provided by theapplication that is executing on behalf of the client 102, that isexecuting and remotely to the client 102, and that is accessing the datacontent object. The contextual information may include informationregarding actions performed, at the request of a user at the client 102,by the ASP system 104 and outside of the application executing on behalfof the client 102. The contextual information can relate to operationssuch as uploading, through the ASP system 104, data content objects tostorage external to the ASP system 104 (e.g., cloud-based storageservice, such as Dropbox®), or downloading content, through the ASPsystem 104, from storage external to the ASP system 104. The contextualinformation can also relate to operations such as a user at the client102 requesting the ASP system 104 share some or all of a data contentobject, or share a space with another user.

As described herein, as data content objects are accessed by the client102 through the ASP system 104, the ASP system 104 can provide theclient 102 with at least some contextual information relating to thedata content objects being accessed. In accordance with embodimentsdescribed herein, the ASP system 104 may present the contextualinformation to the user at the client 102 as the data content object isbeing accessed (e.g., data content object is being viewed) via a spaceprovided by the ASP system 104 to the client 102 and/or via a remotelyexecuting application being accessed by the client 102 through the ASPsystem 104.

In some embodiments, the ASP system 104 can inform the user at theclient 102 regarding events relating to data content objects beingaccessed through the ASP system 104, and may do so based on therelevancy of the event to the user. Events relating to a data contentobject may be relevant to the user based on, for example, the user'spreferences (e.g., based user-defined criterion), the user's previousaccess of the data content objects, and/or the user's association withthe data content object (e.g., user associated with data content objectbased through their common association with a specific workspace).

As the ASP system 104 detects an event associated with a data contentobject being accessed through the ASP system 104, the ASP system 104 canpresent one or more users with a reference to a location in the datacontent object that relates the event. As described herein, a referenceonce presented to a user at the client 102, can be traversed by the userto the location referenced. Such traversal can result in the ASP system104 providing the client 102 with access to an application that isexecuting on behalf of the client 102 and that is accessing the contentof the data content object at the location referenced.

FIG. 2A is a block diagram illustrating an exemplary environment 200utilizing an exemplary system for supporting social productivity inaccordance with various embodiments. In particular, FIG. 2A presentsfurther details regarding the client 102 and the ASP system 104 inaccordance with some embodiments. As shown, the client 102 comprises aclient module 202. The ASP system 104 comprises an access server module204, a storage module 206, a virtualization module 208, an applicationmodule 210, a context module 212, a workspace module 214, a dashboardmodule 216, and a message notification module 218.

For some embodiments, the client module 202 may be configured tofacilitate communication between the client 102 and the ASP system 104,provide a user at the client 102 with a client user interface configuredto facilitate user interaction with the ASP system 104, relay user inputreceived through the client user interface (from the user at the client102) to the ASP system 104, and relay output (e.g., video, audio, orother) from an application provided by the ASP system 104 to one or morecomponents of the client 102 configured to receive and present theoutput through the client user interface (e.g., video output to thevideo display of the client 102, and audio data to the sound processorof the client 102).

For some embodiments, the client module 202 may provide the client userinterface by generating the client user interface at the client 102 andthen presenting the client user interface to a user through a displaydevice (e.g., video display of a tablet computing device) of the client102. Additionally, some embodiments may provide the client userinterface by generating the client user interface at the ASP system 104(e.g., in the access server module 204), and then sending the generatedclient user interface from the ASP system 104 (e.g., the access servermodule 204) to the client module 202 for presentation to the user (e.g.,through a display device coupled to the client 102). In general, thepresented client user interface is a graphical user interface (GUI)adapted for user interaction through the client 102 and its coupledperipherals, which may include a touch screen. Those skilled in the artwill appreciate that the configuration, appearance, and behavior of theclient user interface provided by the client module 202 may vary basedon, among other things, the type of digital device comprising the client102 or the computing resources of the client 102 available to the clientmodule 202 (e.g., peripherals available to the client 102, or modes ofinput available through the client 102).

The client module 202 may further be configured to receive and relaycontrol information from an input device (e.g., peripheral) coupled tothe client 102 (e.g., physical or on-screen keyboard integrated into theclient 102, or peripheral externally communicatively coupled to theclient 102) to the ASP system 104. Likewise, the client module 202 mayrelay control information, or other data, between devices(communicatively) coupled to the client 102 and the ASP system 104(e.g., the client module 202 relays print data from the ASP system 104to a printer coupled to the client 102).

The client module 202 may be also configured to provide an interface atthe client 102 operable in presenting one or more features relating tosocial productivity as described herein. For example, the client module202 may provide an interface enabling access to contextual informationregarding data content objects, an interface presenting or otherwisefacilitating a workspace or other space, an interface presenting orotherwise facilitating a dashboard, and an interface facilitatingnotification services relating to social productivity through the ASPsystem 104.

For example, the client module 202 may be further configured to providea workspace interface at the client 102 operable in presenting one ormore data content objects (e.g., files), stored on one or more separateand disparate cloud-based storage services (e.g., third-party services)or stored locally at the client 102, for access through the client 102.For some embodiments, the workspace interface may allow a user at theclient 102 to request workspace operations with respect to the datacontent objects presented through the workspace interface. The datacontent object presented may include those locally stored and/or thosestored on various cloud-based storage services external to the ASPsystem 104. The workspace operations supported may include adding,deleting, renaming, and moving data content objects stored on one ormore cloud-based storage services or locally at the client 102. Datacontent objects, such as files, presented through the workspaceinterface may be selectable for opening through the ASP system 104,possibly through a virtualized application instance accessed through theASP system 104.

In some embodiments, the client module 202 includes a runtimeapplication compatible with the operating system of the client 102 andthat is a native application of the client 102. Additionally, theruntime application may be configured to provide facilitate access bythe client 102 to data content objects, applications, and socialproductivity features provided through the ASP system 104. In this way,the client module 202 and its runtime application may provide access todata content objects or applications that may be incompatible with theoperation system of the client 102 or that may otherwise not be operableon the client 102 without the use of the client module 202. In this way,the client module 202 may also facilitate access to uniform and agnosticaccess to data content objects residing on one or more different storagelocations external to the client 102 and the ASP system 104, such aslocation provided by different cloud-based storage services (e.g.,Dropbox, Box, etc.). Additionally, the client module 202 may enablevarious social productivity features described herein, such as thoserelating to context for data content objects, workspaces, anddashboards.

Those skilled in the art will appreciate that in some embodiments,access to data content objects, applications, and social productivityfeatures through the ASP system 104 may be facilitated by a third-partycommunication application, such as a web browser application often usedto access web pages.

The client module 202 may also be configured to provide universal and/oragnostic management access to various data content objects that arestored at separate and disparate data storage services but madeavailable through the ASP system 104. Accordingly, in some embodiments,the client module 202 may comprise a management interface adapted toreceive user requests for management operations, such as adding (e.g.,by creation of a new file or by upload), deleting, moving, and renamingdata content objects. For some embodiments, the client module 202 mayutilize web-based application programming interfaces (APIs), which maybe associated with one or more web applications (e.g., Google® Docs), toaccess files stored on cloud-based services. For example, in order tolist data content objects accessible through the ASP system 104, theclient module 202 may utilize web-based APIs for a given cloud-basedservice (e.g., Dropbox, Box, or Google® Docs) to directly performmanagement operations (e.g., listing of stored files, adding files,deleting files, or renaming files) with respect to that service. Then,when a data content object listed through the client module 202 isselected for opening through the ASP system 104, the client module 202may instruct the ASP system 104 to obtain a copy to the selected datacontent object from it respective storage source (e.g., cloud-basedstorage source or local storage source) or directly access the datacontent object from its respective storage source. Thereafter, the ASPsystem 104 may initiate a virtualized application instance having accessto the selected data content object, and the output data of thevirtualized application instance may be transmitted to the client 102.

According to some embodiments, when the data content objects fromdifferent storage services (e.g., different third-party cloud-basedstorage services and/or locally stored at the client) are presented(e.g., through a workspace presented in a segregated manner according totheir storage source (e.g., grouped according to storage source orprojects), or presented in a common pane with little or no indication ofa data content object's storage source. In some embodiments, when a datacontent object presented through the interface is selected for opening,the ASP system 104 may access the data content object directly from itscorresponding storage source (e.g., cloud-based storage service or localstorage at the client) or obtain a cached copy of the data contentobject selected its corresponding storage source, and then present thedata content object for access through a virtualized applicationinstance. Where a cached copy of the data content object is utilized foropening the data content object, the ASP system 104 may be configured tocommit any changes/update performed on the cached copy to the originalcopy at the original storage location (e.g., commitment occurs when thevirtual application instance is closed).

By providing an interface having universal and/or agnostic access to oneor more disparate data storage services and/or the local storage source,various embodiments can provide users (e.g., at the client 102) with aworkspace, through which data content objects stored in disparatelocations can be universally/agnostically accessed for collaborativemanagement, viewing, or editing purposes. FIGS. 18-23 present exampleclient user interfaces that, according to some embodiments, could bepresented by the client module 202 at the client 102.

Continuing with reference to FIG. 2A, the access server module 204 maybe configured to facilitate user access (e.g., by a user at the client102) to data content objects, applications, or social productivityfeatures (e.g., contextual information, workspaces, dashboard, etc.)that are provided through the ASP system 104. In some embodiments, theaccess server module 204 may achieve this by performing some or all ofthe following on behalf of a user accessing the ASP system 104 from theclient 102: (a) establishing and maintaining communication between theclient 102 and the ASP system 104; (b) authenticating access to the ASPsystem 104 (and its various components) by the user; (c) establishingand maintaining one or more application access sessions (also referredto herein as “application sessions”) for the user, whereby eachapplication access session may comprise an instance of an application(e.g., an instance of a particular version of an application) beingexecuted or controlled by the ASP system 104 on behalf of the user atthe client 102; (d) implementing user preferences and settings for theuser's access of the ASP system 104; (e) implementing and enforcing userpolicy on the user's access of the ASP system 104; (f) enabling accessby the applications being executed or controlled by the ASP system 104to data content objects (e.g., files) stored on or stored usingthird-party data storage services (e.g., third-party cloud-based storageservices, such as Dropbox or Google® Docs); (g) monitoring the user'saccess of the ASP system 104; (h) maintaining statistics or analyticsbased on the user's access of the ASP system 104; and (i) facilitatingbilling of the user based on their access or usage of the ASP system104.

The access server module 204 may perform some or all of the followingwhen the ASP system 104 provides social productivity features to theclient 102: (a) interacting with the context module 212 to provide orotherwise facilitate social productivity features that relate tocontextual information for data content objects accessed through the ASPsystem 104; (b) interacting with the workspace module 214 to provide orotherwise facilitate presentation of a workspace (or another space) tothe client 102 by the ASP system 104; (c) interacting with the dashboardmodule 216 to provide or otherwise facilitate presentation of adashboard to the client 102 by the ASP system 104; and (d) interactingwith the message notification module 218 to provide or otherwisefacilitate notifications (e.g., e-mails, instant messages, or pushnotifications), to the client 102 in regard to events relating to datacontent objects accessed through the ASP system 104.

In some embodiments, the access server module 204 may on behalf of theclient 102, negotiate, establish and otherwise facilitate theestablishment of a connection between the client module 202 and anapplication being provided via the virtualization module 208 and theapplication module 210. Once established, the access server module 204may continue to monitor or control the connection, possibly inaccordance with user preferences, settings, and policies utilized by theASP system 104.

The access server module 204 may further be configured to manage theoverall operation of the ASP system 310 discussed further herein. Forexample, the access server module 204 may be operable to track andmanage resources for the ASP system 104, which may involvemonitoring/managing computer resource utilization (e.g., memoryutilization, processor utilization, or network bandwidth utilization) byvarious components of the ASP system 104 or cloud-based services (e.g.,SaaS, PaaS, or IaaS) utilized by various components of the ASP system104. As another example, the access server module 204 may be responsiblefor distributing the workload of serving two or more clients similar tothe client 102 across one or more access servers performing theoperations of the access server module 204.

The storage module 206 may be configured to establish and/or maintainaccess to data on third-party data storage services by an applicationexecuting or being controlled by the ASP system 104 on behalf of theuser at the client 102. In some embodiments, the storage module 206 mayachieve this by receiving, storing, and utilizing access parameters(e.g., third-party access parameters such as protocol information,username, password, encryption key, signature file identifier,navigation address, third-party storage identifier, or the like)provided by the user (at the client 102) in association with athird-party data storage service (e.g., a cloud-based data storageservice, such as Dropbox or Google® Docs) which the user wishes toaccess through the ASP system 104. For example, when the user requestsaccess to data content objects (e.g., files) stored using a third-partydata storage service, the storage module 206 may establish a connectionwith the third-party data storage service using the stored accessparameters (e.g., protocol information, username, password, encryptionkey, signature file identifier, navigation address, third-party storageidentifier, or the like) provided by the user, retrieve a listing of thedata content objects stored on/using or otherwise made available throughthe third-party data storage service in association with the accessparameters provided, and access the data content objects according tothe user's access request. Depending on the embodiment, the user maycause data content objects stored on the third-party data storageservice to be accessed by the ASP system 104, for example, when the userrequests to review a listing of data content objects (e.g., files)stored on the third-party data storage service or when the user choosesto access data content objects (e.g., open, view, or edit a file) usingan application provided by the ASP system 104 (e.g., through theapplication module 210).

In addition to establishing and/or maintaining access to data onthird-party data storage services (e.g., Dropbox, Box, or Google® Docs),the storage module 206 may be configured to permit the ASP system 104 tomanage data content objects on the third-party data storage services onbehalf of the client 102. For instance, the storage module 206 maypermit the ASP system 104 to implement data content object managementfunctions (e.g., workspace functions) with respect to data contentobjects stored on disparate third-party data storage services, therebyenabling a user at the client 102 to perform data content objectsmanagement operations through the client module 202. According to someembodiments, the storage module 206 may be operable with the clientmodule 202 such that users can utilize data content object managementfunctions through a data content object manager interface (e.g., adashboard or a workspace graphical user interface) presented by theclient module 202.

The virtualization module 208 may be configured to establish, monitor,maintain, or otherwise manage execution of an instance of an applicationin a virtual computing environment (hereafter, also referred to as a“virtualized application instance”) for access by the user at the client102. An instance of the application may be executed in a virtualcomputing environment in association with an application sessionestablished for access by the user at the client 102. Accordingly, insome embodiments, the virtualization module 208 may initiate or manageexecution of an instance of the application based on requests receivedfrom the access server module 204.

In some embodiments, the instance of an application, which is operatedin a virtual computing environment for the benefit of user access, maybe based on a particular version of the application. Depending on theembodiment, the version of the application chosen/selected for executionas the application instance may be determined by the access servermodule 204, the virtualization module 208, the application module 210,or some combination thereof. Factors influencing the determination ofthe version may include, for the example, the number of user licensesavailable for a given version of the application, the type of data to beaccessed by the application (e.g., file has a format A that iscompatible with a version B of the application), the user accessing theapplication (e.g., user's access privileges or user's subscription typewith respect to the ASP system 104), the capabilities of the clientdevice 102 (e.g., the client device 102 is equipped with ahigh-definition display compatible with the high-definition output of aparticular version of an application), the computing resources presentlyavailable to the ASP system 104, or network bandwidth required toprovide the client 102 with access to the given version of theapplication. In some embodiments, the virtualization module 208 mayutilize an internal hypervisor or interface with an external hypervisorconfigured to manage execution of the instance of an application in avirtual computing environment. Additionally, the virtualization modulemay employ the use of a cloud-based services (e.g., SaaS, IaaS, orPaaS), possibly provided by a third-party (e.g., Amazon® EC2®, GoGrid®,or Rackspace®), to execute the instance the instance of an applicationin the virtual computing environment.

In various embodiments, the virtualization module 208 of the ASP system104 may initiate any number of virtualized application instances. Forexample, the virtualization module 208 may initiate (e.g., commandinitiation of) any number of virtualized application instance by the ASPsystem 104 and/or any number of servers (e.g., other ASP systems 104and/or other servers). In some embodiments, the virtualization module208 creates and executes a local virtualization environment.

The application module 210 may be configured to obtain or retrieve aversion of an application for execution in a virtual computingenvironment for access by the user at the client 102. For example, theapplication module 210 retrieves a version of the application on behalfof the virtualization module 208, and then provides the retrievedversion to the virtualization module 208 for execution in a virtualcomputing environment. Depending on the embodiment, the applicationmodule 210 may retrieve the version of the application based on arequest from the virtualization module 208 or the access server module204 (e.g., which, as described herein, may be responsible for managingapplication sessions for the user access). The application module 210may retrieve the version of the application from an applicationrepository (not shown), which for some embodiments may be implementedusing one or more file servers, database servers, or some combinationthereof. For example, the version of the application may be retrievedfrom a cloud-based services configured to serve the version of theapplication (e.g., to the application module 210) upon request. Theapplication repository may store a variety of versions for a givenapplication (e.g., for Microsoft® Word®, the application repository maystore Word® 2011, Word® 2008, Word® 2004, and Word® 2001), and providethe appropriate version of the given application based on the requestdiscussed above. Each version of the application may be stored on theapplication repository as a single, separate application executablefile, as a directory containing the version's associated executablefile(s) and any supporting files (e.g., software library files), or as abinary image or compressed file containing the version's associatedexecutable file(s) and any possible supporting files (e.g., softwarelibrary files), or some combination thereof.

For some embodiments, retrieval of the version of the application maycomprise the application module 210 retrieving a path or link to data(e.g., a copy of the application or an image of the application)corresponding to the version of the application to be retrieved. Thispath or link to the data may then be conveyed by the application module210 to the virtualization module 208, which uses the data at thepath/link to instantiate a virtualized application instance.

For some embodiments, the virtualization module 208 and the applicationmodule 210 may be implemented as single module (not shown) that utilizesa cloud-based service (e.g., SaaS, IaaS, or PaaS) to provide a versionof an application executing in a virtual computer environment. Such acloud-based service may be provided by a third-party cloud-basedservice, which may be manage or controlled by the ASP system 104 usingAPIs compatible with the service.

To utilize the cloud-based services for the virtualization module 208,the application module 210, and possibly other components of the ASPsystem 104, the ASP system 104 may employ application programminginterfaces (APIs) (e.g., those provided by Amazon®, GoGrid®, orRackspace®) that permit the ASP system 104 and its various components toprovision (e.g., request the use of), consume, and release servicesprovided by cloud-based services. For example, the virtualization module208 may utilize an Infrastructure-as-a-Service (IaaS) API (e.g., driver)to provision one or more virtual machines to operate one or morevirtualized application instances, while the application module 210 theIaaS API to for provisioning virtual machines to store copies/images ofapplications (utilized by the virtualization module 208 to instantiatevirtualized application instances).

The context module 212 may be configured to provide or otherwisefacilitate capturing and maintaining contextual information regardingdata content objects accessed by the client 102 through the ASP system104. In some embodiments, the context module 212 may detect an eventthat occurred with respect to a data content object accessible throughthe ASP system 104, where the event may be a result of an actionperformed on the data content object through the ASP system 104 at arequest of a first user at the client 102. Upon detecting the event, thecontext module 212 may capture contextual information relating to theevent in a history buffer. Subsequently, the contextual informationcaptured by the context module 212 may be retained to support varioussocial productivity features provided by the ASP system 104, includingthose provided by the workspace module 214 or the dashboard module 216.Additionally, the context module 212 may provide a reference based onthe contextual information, where the reference enables a second user(e.g., at another client) to traverse to a location in the data contentobject relating to the event. For example, when the second user selectsto traverse the reference, the traversal may cause the ASP system 104 toinstruct an application, being controlled by the ASP system 104 andbeing executed on behalf of the second user, to access the data contentobject and move to the location associated with the reference.

The context module 212 may also be configured to create, or facilitatethe creation of, an activity stream for data content objects based onthe contextual information captured by the context module 212. Forexample, the context module 212 may provide the contextual informationcaptured to the workspace module 214, which may be configured to createand present an activity stream for a data content object in connectionwith a workspace (or other space). Likewise, the context module 212 mayprovide the contextual information captured to the dashboard module 216to update or create an activity stream in relation to a data contentobject.

The workspace module 214 may be configured to provide or otherwisefacilitate presentation of a workspace (or another space) to the client102 by the ASP system 104. In some embodiments, the workspace module 214may associate a data content object with a workspace, possibly at therequest of a user at a client (e.g., the client 102). The workspacemodule 214 may detect an event that occurred with respect to the datacontent object accessible through the ASP system 104. The event may be aresult of an action performed on the data content object through the ASPsystem 104 at a request of a first user at the client 102. Based on thedetect event, the workspace module 214 may inform a second user (e.g.,at another client) of the event, where the second user may be associatedwith the workspace.

The workspace module 214 may, at the request of the first user at theclient 102, delegate a task to another user (e.g., the second user) inassociation with at least a portion of content in the data contentobject. The workspace module 214 may, subsequently, receive a responseto the task from the other user (e.g., the second user), and integratethe response into the portion of content. Additionally, the workspacemodule 214 may inform the first user at the client 102 regarding theresponse received from the other user (e.g., the second user), and mayfurther inform the first user of the integration of the response intothe portion of content originally delegated.

For some embodiments, when a first user delegates a task to another userin association with a portion of content in a data content object, theother user may be limited to providing a response for only that portionof content. Additionally, the integration of the response into thecorresponding portion may only affect the portion associated with thetask. Depending on the embodiment, the response provided by the otheruser may be a revised version of the content portion associated with thedelegated task.

The dashboard module 216 may be configured to provide or otherwisefacilitate presentation of a dashboard to the client 102 by the ASPsystem 104. In some embodiments, the dashboard module 216 may detect anevent that occurred with respect to a first data content objectaccessible through the ASP system 104. The event may be a result of anaction performed on the first data content object through the ASP system104 at a request of a first user at the client 102. The dashboard module216 may determine whether an attribute of the first event satisfies acriterion. An attribute of the event evaluated for a criterion caninclude, for example, attributes of the data content object relating tothe event (e.g., type of data content object, size, owner, date created,date modified, etc.), the type of event, the time of the event, the dateof the event, the user causing the event, the identity of theapplication involved in the event, and the type of application involvedin the event. Where the attribute of the event is determined to satisfythe criterion, the dashboard module 216 may provide a first cardrelating to the event and configured to be presented to a second user ata second client. When presented, the first event card may be presentedthrough a dashboard configured to present the second user with eventsrelating to other data content objects in conjunction with the firstevent card. By the use of one or more criteria, the dashboard module 216can implement noise and relevancy controls that determine which eventsare presented to the second user at the second client, and at what time.

For example, through one or more criteria, the dashboard module 216 canimplement one or more threshold conditions (e.g., based on time, date,count of event, type of event, frequency of event, etc.) for determiningrelevancy of data content objects and events when presenting relatedevent cards on a dashboard. The threshold condition may be defined by orevaluated according to a numerical value that controls the granularityof the threshold condition. For example, for a numerical value thatranges between 1 and 10, a numerical values closer to 1 can cause thethreshold condition to be adjusted such that the dashboard module 216presents more events regarding data content objects, and a numericalvalues closer to 10 can cause the threshold condition to be adjustedsuch that the dashboard module 216 presents less events regarding datacontent objects.

Additionally, a threshold condition, implemented by criteria, can definesuch user-based relevancy conditions as: did the user recently createthe data content object, did the user recently change the data contentobject; has the user commented on the data content object; has the userreviewed the content of the data content object; or has the usercollaboratively worked with another user that has changed or otherwiseaccessed the data content object.

The message notification module 218 may be configured to provide orotherwise facilitate notifications to the client 102 from the ASP system104. In some embodiments, the message notification module 218 may beconfigured to cause the transmission of a message from the ASP system104 to the client 102 that notifies a user at the client 102 of eventsthat may have recently transpired and/or that may be of relevance to theuser (e.g., based on one or more criteria). Depending on the embodiment,the message transmitted by way of the message notification module 218may use one or more different means of communication including, forexample, an e-mail, a mobile text message, a push-based notificationsystem, and a social networking service. According to some embodiment,the message notification module 218 may interface with the messagingservice server 112 to cause the transmission of the message from the ASPsystem 104 to the client 102. In various embodiments, the messagenotification module 218 may utilize a messaging system internal to, andprovided by the, the ASP system 104.

FIG. 2B is a block diagram illustrating the storage module 206configured to establish or maintain access to data on third-party datastorage services (e.g., Dropbox, Box, or Google® Docs) by an applicationexecuting or being controlled by the ASP system 104 on behalf of theuser at the client 102. In addition to storing and utilizing accessparameters in association with different data storage services (e.g.,third-party cloud-based storage), the storage module 206 may comprisevarious application programming interfaces (APIs) that facilitate accessto the different storage services over network connections 228. Forexample, as illustrated in FIG. 2B, the storage module 206 may compriseDropbox APIs 220 enabling access data stored at a Dropbox cloud-basedstorage server 230, Box APIs 222 enabling to access data stored at a Boxcloud-based storage server 232, and Google® Docs APIs 224 configured toaccess data stored at a Google® Docs cloud-based services 234. In someembodiments, the web APIs utilized by the storage module 206 maycomprise web-based APIs (e.g., web application APIs) provided by suchthird-party cloud service operators as Dropbox and Google® for accessingvarious cloud-based service, including storage services and filemanagement services.

As also illustrated in FIG. 2B, the storage module 206 may comprisenetwork-protocol based storage APIs 226 that permit access to a networkfile system 236 using non-web-based methodologies. For certainembodiments, the storage module 206 may utilize the network-protocolbased storage APIs 226 to access file system based on various networkprotocols including, for example, Network File System (NFS), Samba, filetransfer protocol (FTP), and the like.

FIG. 3 is a block diagram illustrating an exemplary environment 300utilizing an exemplary system for supporting social productivity inaccordance with various embodiments. As shown, the exemplary environment300 comprises clients C₁ to C_(n) (represented by clients 302, 304, and308), an application service provider (ASP) system 310, and a network324 enabling communication between the clients 302, 304, and 308 and theASP system 310 over network connections 326. Depending on theembodiment, the clients 302, 304, and 306 may be similar in function andimplementation to the client 102, and the ASP system 310 may be similarin function and implementation to the ASP system 104, each of which wasdiscussed in detail with reference to FIGS. 1 and 2. As such, inaccordance with various embodiments described herein, the clients 302,304, and 306 may comprise one or more digital device(s) configured tocommunicating with the ASP system 310 through the network 324, the ASPsystem 310 may comprise one or more server configured to provide theclients 302, 304, and 306 with access to files, applications, and socialproductivity features.

As further shown in FIG. 3, the functionality of the ASP system 310 maybe implemented by way of access servers ACS₁ to ACS_(n) (represented byaccess servers [ACSs] 312, 314, and 316), and application servers APS₁to APS_(n) represented by (application servers [APSs] 318, 320, and322). Although a limited number of clients, ACSs, and APSs are depictedin FIG. 3, those skilled in the art will appreciate that there may beany number of clients, ACSs, and APSs. Ellipses 306 in FIG. 3 indicatethat any number of clients, ACSs, and APSs could be present in theexemplary environment 300.

In some embodiments, the ACSs 312, 314, and 316 may implement some orall of the functionality provided by the access server module 204 asdescribed in reference to FIG. 2A, and the APSs 318, 320, and 322 mayimplement some or all of the functionality provided by some or all ofthe storage module 206, the virtualization module 208, the applicationmodule 210, the context module 212, the workspace module 214, thedashboard module 216 and the message notification module 218 asdescribed in reference to FIG. 2A. Specifically, according to someembodiments, the workload of providing some or all of the services orfunctionalities of the access server module 204 may be distributedamongst some or all of the ACSs 312, 314, and 316, and the workload ofproviding, while the workload of providing some or all of the servicesor functionalities of the storage module 206, the virtualization module208, the application module 210, the context module 212, the workspacemodule 214, the dashboard module 216 and the message notification module218 may be distributed amongst some or all of the APSs 318, 320, and322. In some instances, the ACSs 312, 314, and 316 may utilize loadbalancing to distribute the workload amongst the available ACSs, and theAPSs 318, 320, and 322 may utilize load balancing to distribute theworkload amongst the available APSs. In various embodiments, one or moredigital devices may manage and/or provide load balancing to any numberof ACSs and/or any number of APSs. By distributing the workload amongstmultiple ACSs and APSs, certain embodiments may provide acceptableperformance (e.g., enough availability of computing resources to providethe requested applications with user-acceptable performance),scalability (e.g., near real-time user scalability according to demandor the number of users currently utilizing the ASP system 310 increasesor decreases, or application scalability to provide more variety ofapplications operating on a variety of operating systems), andreliability (e.g., through redundancy of servers and components, orlower bandwidth per user) with respect to the ASP system 310.

In the example illustrated in FIG. 3, a dashed line 328 illustrates avirtual communication channel (hereafter referred to as “virtualcommunication channel 328”) between the client 304 and the applicationservers 318, 320, and 322 established via the access server 312. In someembodiments, the virtual communication channel between the client 304and the application servers 318, 320, and 322 may be implemented by wayof one or more network connections 326 between the client 304 and theaccess server 312, and one or more networks connections 326 between theaccess server 312 and each of the application servers 318, 320, and 322.Alternatively, in some embodiments, the virtual communication channelbetween the client 304 and the application servers 318, 320, and 322 maybe implemented by the access server 312 mediating one or more networkconnections 326 directly between the client 304 and each of theapplication servers 318, 320, and 322.

Once established, the virtual communication channel 328 enables dataflow over the network connections 326 between the client 304 and theaccess server 312, and data flow between the client 304 and theapplication servers 318, 320, and 322 via the access server 312. Throughsuch the data flows, the client 304 may, for example, be serviced by theaccess server 312 (e.g., in accordance with the access server module 204described in FIG. 2A) or obtain access to application services andsocial productivity features provided by each of the application servers318, 320, and 322 (via the access server 312).

FIG. 4 is a block diagram illustrating an example context module 212that is part of an example system for supporting social productivity inaccordance with various embodiments. As shown, the context module 212comprises an event module 402, a capture module 404, a history buffermodule 406, a reference module 408, and a traversal module 410.

The event module 402 may be configured to detect an event that occurredwith respect to a data content object accessible through the ASP system104. The event may be one resulting from an action performed on the datacontent object through the ASP system 104 at a request of a first userat the client 102. As such, the event module 402 may determine eventsbeing performed on a data content object, by a user, using adata-content object processing application. As described herein, anevent can comprise: an operation being performed on content of the datacontent object being accessed the ASP system 104 (e.g., reading,creating, modifying, removing, inserting, and moving content): creating,removing, uploading, or downloading the data content object through theASP system 104; a user sharing the data content object with another userthrough the ASP system 104; or associating or disassociating the datacontent object to a workspace or a tag through the ASP system 104.Events can comprise a temporal-oriented, location-oriented, orrelationship-oriented change for the data content object.

For certain embodiments, the event module 402 may detect an event withrespect to a data content object by monitoring interactions between theclient 102 and the ASP system 104 as the first user at the client 102accesses a data content object through the ASP system 104. For example,as the client 102 requests an application controlled by the ASP system104 to insert, move, delete, change, or otherwise access content in thedata content object, the event module 402 can monitor such operationrequests and detect event accordingly. For particular embodiments, theevent module 402 may detect an event when an application remotelyexecuting on behalf of the client 102 informs the event module 402 (orsome other module of the ASP system 104) regarding operations beingperformed on content of the data content object at the request of theclient 102. For instance, the application remotely executing on behalfof the client 102 may provide the event module 402 (or some other moduleof the ASP system 104) with a listing of such operations and/or changesresulting from such changes.

The capture module 404 may be configured to capture contextualinformation relating to the event detected by the event module 402, andto store the captured contextual information (e.g., indications fordetected events) using the history buffer module 406. The contextualinformation can comprise user information, date information, timeinformation, or location information in relation to the detected event.For some embodiment, the contextual information may comprise informationprovided by an application performing the action that results in theevent. For example, where the application performing the action is onebeing controlled by the ASP system 104 and being executed on behalf ofthe first user at the client 102, the application may provide metadatarelating to the action. In another example, the application may providea listing of changes implemented to the data content object by theapplication at the request the first user at the client 102. The listingmay comprise an array of changes implemented by the application, withthe changes possibly being sorted according to time of implementation(e.g., oldest to most recent change). The application may provide such alisting of changes when the application is instructed (e.g., by the userat the client) to save the save/commit the changes implemented to thedata content object to storage. As described herein, the saving orcommitting changes to the data content object to storage may involveuploading a resulting, changed data content object to a cloud-basedstorage service.

For some embodiments, the application may provide a listing of changessubsequent to the capture module 404 requesting such changes from theapplication (which may occur after an event has been detected). In thisway, the capture module 404 may obtain an event indication and/orinformation by pulling information from the application. Additionally,in some embodiments, the application may provide a listing of changes tothe capture module 404 without need for request by the capture module404. In this way, the application can push an indication and/orinformation regarding an event to the capture module 404, possibly asthe event is occurring at the application or soon after. Depending onthe embodiment, the capture module 404 may receive event indicationsand/or information according to a schedule, based on satisfaction ofcertain conditions (e.g., occurrence of a specific type of event), orsome combination thereof. It will be appreciated that the applicationmay provide the capture module 404 with indications and/or informationfor events other than those relating to changes to a data contentobject.

In some embodiments, the event indications and/or information providedby an application to the capture module 404 may vary based on thefeatures or capabilities of the application. For instance, the featuresor capabilities of a given application may determine the amount ofinformation provided for events and/or for what event types the givenapplication can provide an indication.

The capture module 404 may capture, and facilitate retention of,contextual information in relation to a data content object. Asdescribed herein, the retained contextual information can supportvarious social productivity features provided by the ASP system 104,including those provided by the workspace module 214 or the dashboardmodule 216.

The history buffer module 406 may be configured to store contextualinformation captured by the capture module 404. Depending on theembodiment, the history buffer module 406 may maintain a separatehistory buffer for each data content object, a separate history bufferfor each workspace, or an alternative configuration of history buffers(e.g., per a user interacting with a data content object). The historybuffer module 406 may store contextual information for a data contentobject in a table (e.g., database table), where the table may have oneor more of the following fields: file version field, operation sequencenumber field, object path field, operation field, operation data field,time field, user field, and change field.

The file version field may provide a modification time or a storageversion number for the data content object relating to the contextualinformation being stored. The operation sequence number field mayidentify the historical version of the data content object relating tothe contextual information being stored. The object path may provide apath (or some other identifier) to the data content object relating tothe contextual information being stored. An example of the path mayinclude “filename/section #/paragraph #” for a word processing documentfile, “filename/sheet #” for a spreadsheet document file, and“filename/slide #” for a presentation document file. The operation fieldmay provide information identifying the operation performed on the datacontent object relating to the contextual information is being stored.Examples of operations that can be identified by the field can includeinsert, delete, change, read, and the like. The operation data field mayprovide data facilitating a redo operation, an undo operation, or someother complex operations with respect to the content of the data contentobject relating to the contextual information being stored. The timefield may indicate the time for the event that resulted in thecontextual information that being stored. The user field may indicateone or more users that caused the event relating to the contextualinformation that being stored. The change field may provide text, image,or some other type of content that presents or summarizes the effect(e.g., change), of the event, on the content of the data content object.

For some embodiments, some or all of the foregoing fields may facilitateoperational transformations with respect to content of a data contentobjects associated with the contextual information. In variousembodiments, some or all of the foregoing fields can be also used touniquely identify a version of a data content object. For example, aunique object identifier can comprise an operation sequence number andan object path, which may facilitate use of the unique object identifierwhen accessing various versions of data content objects through the ASPsystem 104 (e.g., via the client 102 or via an API).

The history buffer module 406 may be configured to maintain andsubsequently provide contextual information to support various socialproductivity features provided by the ASP system 104, including thoseprovided by the workspace module 214 or the dashboard module 216. Invarious embodiment, the history buffer module 406 captures indicationsand/or information relating to various types of events that occur inassociation with a data content object.

For example, where the event is a change to the content of a datacontent object, the history buffer module 406 may store contextualinformation regarding the event a table having one or more of thefollowing fields: a change type field, a position field, a summaryfield, a base version field, and a current version field. The changetype field may indicate the type of content change (e.g., insert,update, delete, or move content) that occurred with respect to the datacontent object. The position field can provide data indicating theposition in the content of the data content object where the changeoccurred. For some embodiments, such position information may beutilized when providing a reference to the location for the purposes ofanother user to traverse to the location. The summary field may providea text-based description of the change implemented by the event.Depending on the embodiment, the description stored in the summary fieldmay be user-defined, auto generated, or some combination thereof. Thebase version field may indicate previous version of the data contentobject before the change event. The current version field may indicatethe version of the data content object immediately after the changeevent. In some embodiments, some or all of the foregoing fields mayfacilitate operational transformation with respect to content of datacontent objects relating to the change events.

In another example, where the data content object is a workspace object,the contextual information maintained may include events (e.g., changes)made to the workspace object and/or events that occur with respect todata content objects associated with the workspace object (e.g., changeto a file or people object associated with a workspace corresponding tothe workspace object).

The reference module 408 may be configured to provide a reference basedon the contextual information, where the reference enables a second user(e.g., at another client) to traverse to a location in the data contentobject relating to the event. Once a reference is provided, it may bepresented to the second user for review and/or traversal. For someembodiments, the reference may be a universal resource locator, or someother form of link, which when selected for traversal by a user at aclient, can result in the ASP system 104 to instruct an application,being controlled by the ASP system 104 and being executed on behalf ofthe second user, to access the data content object and move to thelocation associated with the reference.

The traversal module 410 may be configured to receive a request from asecond user (e.g., at another client) to traverse the reference to thelocation in the data content object relating to the event. In responseto the request from the second user, the traversal module 410 mayinstruct an application to traverse to the location corresponding to thereference. For example, the second user can select to traverse thereference and cause the ASP system 104 to instruct an application, beingcontrolled by the ASP system 104 and being executed on behalf of thesecond user, to access the data content object and move to the locationreferenced. Depending on the embodiment, the ASP system 104 may providethe second user with access to the application before, during, or afterthe traversal module 410 instructs the application to traverse to thelocation corresponding to the reference. Additionally, for someembodiments, the traversal module 410 may instruct the applicationthrough the use of one or more other modules of the ASP system 104including, for example the access server module 204, the storage module206, the virtualization module 208, and the application module 210.

FIG. 5 is a block diagram illustrating an example workspace module 214that is part of an example system for supporting social productivity inaccordance with various embodiments. As shown, the workspace module 214comprises an association module 502, an event module 504, an eventnotification module 506, a share module 508, a delegate module 510, anda pivot module 512.

The association module 502 may be configured to determine one or moreusers authorized and designated to receive a notification (e.g., fromthe event notification module 506) about events detected (e.g., by theevent module 504) with respect to a data content object. Such adetermination by the association module 502 may be based on associationof the one or more users with the data content object. The associationmodule 502 may be further configured to permit a user to associate adata content object, accessible through the ASP system 104, withworkspace, or some other type of space. As described herein, a“workspace” can refer to a general space (e.g., system or user-created)that can hold all other types of spaces (e.g., file space, people space,group space, etc.), that can be associated with one or more data contentobjects of one or more types, and that can agnostically augmentdifferent types of data content objects accessed through the workspace.For some embodiments, workspaces can be associated with one or moreusers (e.g., through workspace sharing), and can be associated such thatthe users can have varying levels of access to data content objectsaccessible through the workspace. When accessing a workspace, a user canchoose to access a data content object associated with the workspace,and the workspace may augment such access with contextual informationhistorically gathered in relation to the data content object.

The event module 504 may be configured to detect an event that occurredwith respect to the data content object. The event may be one resultingfrom an action performed on the data content object through the ASPsystem 104 at a request of a first user at the client 102. Additionally,the first user may be associated with the workspace.

As described herein, an event can comprise: an operation being performedon content of the data content object being accessed the ASP system 104(e.g., reading, creating, modifying, removing, inserting, and movingcontent): creating, removing, uploading, or downloading the data contentobject through the ASP system 104; a user sharing the data contentobject with another user through the ASP system 104; or associating ordisassociating the data content object to a workspace or a tag throughthe ASP system 104. Events can comprise a temporal-oriented,location-oriented, or relationship-oriented change for the data contentobject.

As also described herein, the event module 504 may detect an event withrespect to a data content object by monitoring interactions between theclient 102 and the ASP system 104 as the first user at the client 102accesses a data content object through the ASP system 104. For example,as the client 102 requests an application controlled by the ASP system104 to insert, move, delete, change, or otherwise access content in thedata content object, the event module 504 can monitor such operationrequests and detect event accordingly. Additionally, the event module504 may detect an event when an application remotely executing on behalfof the client 102 informs the event module 504 (or some other module ofthe ASP system 104) regarding operations being performed on content ofthe data content object at the request of the client 102. For instance,the application remotely executing on behalf of the client 102 mayprovide the event module 504 (or some other module of the ASP system104) with a listing of such operations and/or changes resulting fromsuch changes.

The event notification module 506 may be configured to provide anotification for a data content object in connection with the eventdetected by the event module 504 (e.g., provide a data-content-objectevent notification). In some embodiments, providing a notification inconnection with the event detected by the event module 504 may involvethe event notification module 506: selecting one or more particularevents in the history buffer (e.g., the history buffer module 406) forwhich notifications may be generated; and generating adata-content-object event notification identifying the one or moreparticular events performed on the first data content object.

In accordance with some embodiments, the notification provided by theevent notification module 506 may include an event card comprising aunit of summarized information regarding the event in association withthe data content object. Once generated, a card can be presented to auser through a workspace to inform them of an event in relation to adata content object. A card can comprise some or all of the contextualinformation captured in association with an event, a comment sectionconfigured to present or receive a comment in association with theevent, or a secondary action (e.g., call of action) configured to beperformed an operation with respect to the card at the request of theuser perceiving the card (e.g., the percipient user). Some examples ofsecondary actions include, entering a comment in association with thefirst card (e.g., liking an event, liking an existing comment, orreplying to a an existing comment); sharing the first card with anotheruser, deferring presentation of the first card (e.g., defer based ontime, date, or another event), assigning a task associated with theevent to another user.

According to some embodiments, a card may generated according to a modelcomprising: an avatar image representing a user associated with anevent; one or more users (e.g., actors) causing the event; a listing ofone or more activities (e.g., verbs) relating to the event (e.g., “User1 performed Activities A, B, and C”); an identifier for the data contentobject; a summary for the event; a comment entered in association withthe event; secondary actions (e.g., calls to action) associated with thecard (e.g., dismiss to archive card, defer card to another time, deletecard, or accept card to indicate that card was accepted or otherwiseacted upon); a date stamp for when the card was presented and/or whenthe event occurred; or noise controls configured to permit the user toadjust visibility of the current card and/or other cards. The summary ofthe event may include may include text, images or other contentdescribing the event and may also include references/links to thelocation in the content relating to the event. Additionally, for someembodiments, the summary may be auto-generated by the event notificationmodule 506 when the event notification module 506 provides the card inresponse to an event. The noise controls can adjust or bypass one ormore criteria that determine which event cards are presented for a userand/or when certain events are presented to the user.

The share module 508 may be configured to share the workspace (or someother space) with the second user at the request of the first user. Thesharing of the space or content to the second user can also result inthe event module 504 detecting the share event and/or the eventnotification module 506 issuing a notification relating to the shareevent.

The share module 508 may be further configured to share at least aportion of content in the data content object with another user at therequest of the first user. For some embodiments, the sharing of a spaceor content of the data content object can result in the second userbeing granted some level of access to the shared space or content,possibly where such access did not already exist. For example, where afirst user shares a portion of content with a file object with a seconduser, the first user may provide the second user with some level ofaccess to the shared content portion. For instance, the second user maybe provided with read and/or write access to only the shared portion ofthe file object, or read access to all content of the file object butread and write access to the shared portion of the file object. In afurther example, where a share event provides the second user with somelevel of editing access to a data content object, edits performed undersuch level of access may be maintained in a separate version associatedwith the user, and may be incorporated into the original version afterapproval by another user (e.g., the first user and/or the user owningthe data content object).

Further, the sharing of the space or content to the second user canresult in the second user being associated with the space or content.Based on such an association, the second user may begin to receive cardsrelating to events that occur with respect to the shared space orcontent. When the first user shares a space or content of the datacontent object with the second user, the first user can implement accesslimitations that can govern the second user's access to the space orcontent, including limitations that determine whether the second usercan share the shared space or content with a third user.

The delegate module 510 may be configured to delegate a task to anotheruser (e.g., the second user) in association with at least a portion ofcontent in the data content object. For some embodiments, the delegationof the task may result in the other user receiving the task (e.g.,description, sender, etc.) and a copy of the portion of contentassociated with the task. In response to the task, the other user maysubsequently access the copied portion in accordance with the taskand/or perform an action with respect to the task. For some embodiments,the response may comprise an action with respect to the task, such asacceptance, rejection, completion or deferment of the task. The responsemay also comprise the copied content portion as revised by the otheruser, where the copied content portion as revised is intended to replaceportion of the content associated with the task.

Subsequently, the delegate module 510 may receive the response to thetask from the other user (e.g., the second user), and act according tothe response received. Where the response comprises an action withrespect to the task, the first user's status of the task will be updatedaccordingly. Where the response comprises content (e.g., copied contentportion as revised), the delegate module 510 may integrate the contentfrom the response into the portion of content associated with the task,possibly by replacing the original portion of content with the contentfrom the response.

When a first user delegates a task to another user in association with aportion of content in a data content object, the other user may belimited to providing a response for only that portion of content. Theintegration of the response into the corresponding portion may onlyaffect the portion associated with the task.

For some embodiment, the delegation of the task by the delegate module510 may result in the other user receiving the task (e.g., description,sender, etc.) and a share to the portion of content associated with thetask. Accordingly, when the other user accesses the shared portion ofcontent, the first user may be informed of such access. Additionally,when the other user accesses the shared portion of content and performschanges on the shared portion of content, such changes may be instantlyreflected in the content of the data content object. As discussedherein, when a share to a portion of content in a data content object isprovided to another user through the delegate module 510, the share mayhave limitations that restrict the other user's access to the sharedportion and/or to the remainder of the content of the data contentobject.

Upon receiving a form of response, the workspace module 214 may informthe first user at the client 102 regarding the response received fromthe other user (e.g., the second user). Where the response is integratedinto the original portion of the content associated with the task, theworkspace module 214 may further inform the first user of theintegration.

As described herein, the first user at the client 102 can choose toaccess one or more data content objects through the perspective ofspaces associated with different types of data content objects (e.g.,file space, people space, group space, project space, tag space, etc.).The pivot module 512 may be configured to pivot between spaces beingprovided to the client 102 according to the type of data content objectbeing accessed. For example, when a user chooses to access a collectionof different types of data content objects through the perspective of asingle workspace, the pivot module 512 can pivot from a workspace to aspecific space when the user selects a data content object associatedwith the space (e.g., pivot to file space when a data content objectthat is a file is selected by the first user). Using the pivot module512, the first user can also choose to pivot between a specific spaceand a general workspace. As shown, the pivot module 512 comprises a filespace module 514 configured to access data content objects that arefiles, a people space module 516 configured to access data contentobjects relating to people, a group space module 518 configured toaccess data content objects relating to groups of people, a projectspace module 520 configured to access data content objects relating to aproject, and a tag space module 522 configured to access data contentobjects relating to tags. Those skilled in the art will appreciate thatother spaces may be included in various embodiments for other types ofdata content objects, including new spaces for data space object createdby third-party providers.

FIG. 6 is a block diagram illustrating an example dashboard module 216that is part of an example system for supporting social productivity inaccordance with various embodiments. As described herein, a dashboardcan be included with a workspace and can be configured to assist usersin productively navigating issues and items of relevance regarding datacontent objects access through the workspace, for example to create,present, publish or share content in data content objects (e.g.,documents, spreadsheets and presentations). As shown, the dashboardmodule 216 comprises an event module 602, a criterion module 604, anevent notification module 606, and a presentation module 608, whichenable the dashboard module 216 to provide or otherwise facilitatepresentation of a dashboard in association with a workspace.

The event module 602 may be configured to detect an event that occurredwith respect to the data content object. The event may be one resultingfrom an action performed on the data content object through the ASPsystem 104 at a request of a first user at the client 102. As describedherein, an event can comprise: an operation being performed on contentof the data content object being accessed the ASP system 104 (e.g.,reading, creating, modifying, removing, inserting, and moving content):creating, removing, uploading, or downloading the data content objectthrough the ASP system 104; a user sharing the data content object withanother user through the ASP system 104; or associating ordisassociating the data content object to a workspace or a tag throughthe ASP system 104. Events can comprise a temporal-oriented,location-oriented, or relationship-oriented change for the data contentobject.

As described herein, the event module 602 may detect an event withrespect to a data content object by monitoring interactions between theclient 102 and the ASP system 104 as a first user at the client 102accesses a data content object through the ASP system 104. For example,as the client 102 requests an application controlled by the ASP system104 to insert, move, delete, change, or otherwise access content in thedata content object, the event module 602 can monitor such operationrequests and detect event accordingly. Additionally, the event module602 may detect an event when an application remotely executing on behalfof the client 102 informs the event module 602 (or some other module ofthe ASP system 104) regarding operations being performed on content ofthe data content object at the request of the client 102. For instance,the application remotely executing on behalf of the client 102 mayprovide the event module 602 (or some other module of the ASP system104) with a listing of such operations and/or changes resulting fromsuch changes.

The criterion module 604 may be configured to determining whether anattribute of the first event satisfies a criterion. For example, thecriterion module 604 may determine whether the one or more particularevent indications satisfy a threshold condition permitting notification(e.g., before the event notification module 606 generates andata-content-object event notification). As described herein, anattribute of the event evaluated for a criterion can include, forexample, attributes of the data content object relating to the event(e.g., type of data content object, size, owner, date created, datemodified, etc.), the type of event, the time of the event, the date ofthe event, the user causing the event, the identity of the applicationinvolved in the event, and the type of application involved in theevent.

To determining whether an attribute of the first event satisfies acriterion, the criterion module 604 may first identify the criterion bywhich the attribute is evaluated. According to some embodiments, thecriterion may be identified according to a second user currentlyaccessing the dashboard and reviewing the event cards being presented bythe dashboard. In some embodiments, the identification of the criterioncan be based on the preferences or user settings of the second user orthe user second user's past activities with respect to data contentobjects accessible through the ASP system 104.

Though the example of FIG. 6 is generally described in terms of a singleeven attribute and a single criterion, those skilled in the art willappreciate various embodiments may involve two or more event attributesand/or two or more criteria. Additionally, though the one or morecriteria used by the criterion module 604 may be identified based on thesecond user, it should be understood that one or more criteria used bythe criterion module 604 may be identified by default (e.g., one or morecriteria applied system-wide) and/or by other factors (e.g., currentsystem load).

Through one or more criteria, the criterion module 604 can implement oneor more threshold conditions (e.g., based on time, date, count of event,type of event, frequency of event, etc.) for determining relevancy ofdata content objects and events when presenting related event cards on adashboard.

In one example, a threshold condition may be defined by or evaluatedaccording to a numerical value that controls the granularity of thethreshold condition. For example, for a numerical value that rangesbetween 1 and 10, a numerical values closer to 1 can cause the thresholdcondition to be adjusted such that the dashboard module 216 presentsmore events regarding data content objects, and a numerical valuescloser to 10 can cause the threshold condition to be adjusted such thatthe dashboard module 216 presents less events regarding data contentobjects.

Additionally, certain threshold conditions can be evaluated by thecriterion module 604 from the perspective of the second user. Forexample, a threshold condition, implemented by criteria, may define suchuser-based relevancy conditions as: did the second user recently createthe data content object, did the second user recently change the datacontent object; has the second user commented on the data contentobject; has the second user reviewed the content of the data contentobject; or has the second user collaboratively worked with another userthat has changed or otherwise accessed the data content object. Thoseskilled in the art would understand that other threshold condition,particular those from the perspective of the second user, are alsopossible.

Where the criterion module 604 determines the attribute of the eventsatisfies the criterion, the event notification module 606 may provide anotification for a data content object in connection with an eventdetected by the event module 602 (e.g., provide a data-content-objectevent notification). In accordance with some embodiments, thenotification provided by the event notification module 606 may include afirst event card (hereafter, “first card”) relating to the event andconfigured to be presented to the second user at a second client. Asdescribed herein, “card” and “event card” can refer to a unit ofsummarized information regarding an event in association with a datacontent object. Once generated, a card can be presented to a userthrough a dashboard to inform them of an event in relation to a datacontent object. A card can comprise some or all of the contextualinformation captured in association with an event, a comment sectionconfigured to present or receive a comment in association with theevent, or a secondary action (e.g., call of action) configured to beperformed an operation with respect to the card at the request of theuser perceiving the card (e.g., the percipient user). Some examples ofsecondary actions include, entering a comment in association with thefirst card (e.g., liking an event, liking an existing comment, orreplying to a an existing comment); sharing the first card with anotheruser, deferring presentation of the first card (e.g., defer based ontime, date, or another event), and assigning a task associated with theevent to another user.

According to some embodiments, a card may generated according to a modelcomprising: an avatar image representing a user associated with anevent; one or more users (e.g., actors) causing the event; a listing ofone or more activities (e.g., verbs) relating to the event (e.g., “User1 performed Activities A, B, and C”); an identifier for the data contentobject; a summary for the event; a comment entered in association withthe event; secondary actions (e.g., calls to action) associated with thecard (e.g., dismiss to archive card, defer card to another time, deletecard, or accept card to indicate that card was accepted or otherwiseacted upon); a date stamp for when the card was presented and/or whenthe event occurred; or noise controls configured to permit the user toadjust visibility of the current card and/or other cards. The summary ofthe event may include may include text, images or other contentdescribing the event and may also include references/links to thelocation in the content relating to the event. Additionally, for someembodiments, the summary may be auto-generated by the event notificationmodule 606 when the event notification module 606 provides the card inresponse to an event. The noise controls can adjust or bypass one ormore criteria that determine which event cards are presented for a userand/or when certain events are presented to the user.

In some embodiments, providing a notification in connection with theevent detected by the event module 602 may involve: the eventnotification module 606 selecting one or more particular events in thehistory buffer (e.g., the history buffer module 406) for whichnotifications may be generated; the criterion module 604 determiningwhether the one or more particular event indications satisfy a thresholdcondition permitting notification; and the event notification module 606generating a data-content-object event notification identifying the oneor more particular events performed on the first data content object.

The presentation module 608 may be configured to present the first eventcard through a dashboard, where the dashboard is configured to presentthe second user with events relating to other data content objects inconjunction with the first event card. According to some embodiments,the dashboard may be provided to and accessed by any user at a clientand currently accessing the ASP system 104. Additionally, as describedherein, the dashboard may vary according to the user accessing thedashboard and one or more criteria associated with the user (which candetermine the relevant event cards to be presented on the dashboard).

Depending on the embodiment, the presentation module 608 may present thedashboard through a graphical user interface (GUI) that enables variousvisual arrangements of event cards to be presented through thedashboard. For example, the presentation module 608 may be configured tovisually arrange the event cards in the dashboard (e.g., tiling eventcards, stack event cards, arranging event cards in columns or rows)according to card categories and/or relevance to the user perceiving thedashboard. As described herein, the criterion module 604 may determinewhat event cards are relevant for presentation on the dashboard by thepresentation module 608.

As shown the presentation module 608 comprises a change module 610, amessage module 612, a task module 614, and a share module 616, each ofwhich can determine the event cards to be presented through thedashboard. The change module 610 may be configured to identify andpresent event cards relating to changes to data content objects relevantto the user accessing the dashboard. The message module 612 may beconfigured to identify and present event cards relating to electroniccommunication relevant to the user accessing the dashboard. The taskmodule 614 may be configured to identify and present event cardsrelating to delegated tasks and data content objects relevant to theuser accessing the dashboard. The share module 616 may be configured toidentify and present event cards relating to shared data content objectsrelevant to the user accessing the dashboard. As described herein,relevancy of a data content object and/or an event can be determined inaccordance with the one or more criteria imposed by the criterion module604.

FIG. 7 is a flowchart illustrating an example method 700 for providingcontext capture that supports social productivity in accordance withvarious embodiments. As shown, the method 700 can begin at step 702,with the event module 402 detecting an event that occurred with respectto a data content object accessible through the ASP system 104. Theevent may be one resulting from an action performed on the data contentobject through the ASP system 104 at a request of a first user at theclient 102.

At step 704, the capture module 404 may be configured to capturecontextual information relating to the event detected by the eventmodule 402. According to some embodiments, the capture module 404 maystore the captured contextual information using the history buffermodule 406, which may subsequently provide contextual information uponrequest.

At step 706, the reference module 408 may be configured to provide areference based on the contextual information, where the referenceenables a second user (e.g., at another client) to traverse to alocation in the data content object relating to the event.

At step 708, the ASP system 104 may present captured contextualinformation through an event card presented through a workspace beingprovided by the workspace module 214 or through a dashboard presented bythe dashboard module 216. With the contextual information, the referenceprovided by the reference module 408 may be presented in the event card,thereby permitting the second user to select the reference for traversalto the event location.

At step 710, the traversal module 410 may be configured to receive arequest from the second user (e.g., at another client) to traverse thereference to the location in the data content object relating to theevent. In response to the request from the second user, at step 712, thetraversal module 410 may instruct an application to traverse to thelocation corresponding to the reference. For example, the second usercan select to traverse the reference and cause the ASP system 104 toinstruct an application, being controlled by the ASP system 104 andbeing executed on behalf of the second user, to access the data contentobject and move to the location referenced. Depending on the embodiment,the ASP system 104 may provide the second user with access to theapplication before, during, or after the traversal module 410 instructsthe application to traverse to the location corresponding to thereference. Additionally, for some embodiments, the traversal module 410may instruct the application through the use of one or more othermodules of the ASP system 104 including, for example the access servermodule 204, the storage module 206, the virtualization module 208, andthe application module 210.

Though the steps of method 700 may be depicted and described in acertain order, those skilled in the art will appreciate that the orderin which the steps are performed may vary between embodiments.Additionally, those skilled in the art will appreciate that thecomponents described above with respect to the method 700 are merelyexamples of components that may be used with the method 700, and thatother components may also be utilized in some embodiments.

FIG. 8 is a flowchart illustrating an example method 800 for a workspacethat supports social productivity in accordance with variousembodiments. As shown, the method 800 can begin at step 802, with theassociation module 502 associating a data content object, accessiblethrough the ASP system 104, with workspace, or some other type of space.

At step 804, the event module 504 may detect an event that occurred withrespect to the data content object. The event may be one resulting froman action performed on the data content object through the ASP system104 at a request of a first user at the client 102. Additionally, thefirst user may be associated with the workspace of step 802.

At step 806, the event notification module 506 may be configured toinform a second user associated with the workspace regarding the eventdetected by the event module 504. According to some embodiments, thesecond user may be associated with the workspace when the share module508 shares the workspace with the second user, possibly based on arequest from the first user at the client 102. Additionally, for someembodiments, the event notification module may inform the second user ofthe detected event by providing an event card relating to the eventdetected by the event module 504.

At step 808, the delegate module 510 may be configured to delegate atask to another user (e.g., the second user) in association with atleast a portion of content in the data content object. For someembodiments, the delegation of the task may result in the other userreceiving the task (e.g., description, sender, etc.) and a copy of theportion of content associated with the task. In response to the task,the other user may subsequently access the copied portion in accordancewith the task and/or perform an action with respect to the task, Forsome embodiments, the response may comprise an action with respect tothe task, such as acceptance, rejection, completion or deferment of thetask. The response may also comprise the copied content portion asrevised by the other user, where the copied content portion as revisedis intended to replace portion of the content associated with the task.

At step 810, the delegate module 510 may receive the response to thetask from the other user (e.g., the second user), and act according tothe response received. Where the response comprises an action withrespect to the task, the first user's status of the task will be updatedaccordingly. Where the response comprises content (e.g., copied contentportion as revised), at step 812, the delegate module 510 may integratethe content from the response into the portion of content associatedwith the task, possibly by replacing the original portion of contentwith the content from the response.

For some embodiment, the delegation of the task by the delegate module510 (at step 808) may result in the other user receiving the task (e.g.,description, sender, etc.) and a share to the portion of contentassociated with the task. Accordingly, when the other user accesses theshared portion of content, the first user may be informed of suchaccess. Additionally, when the other user accesses the shared portion ofcontent and performs changes on the shared portion of content, suchchanges may be instantly reflected in the content of the data contentobject. As discussed herein, when a share to a portion of content in adata content object is provided to another user through the delegatemodule 510, the share may have limitations that restrict the otheruser's access to the shared portion and/or to the remainder of thecontent of the data content object.

Though the steps of method 800 may be depicted and described in acertain order, those skilled in the art will appreciate that the orderin which the steps are performed may vary between embodiments.Additionally, those skilled in the art will appreciate that thecomponents described above with respect to the method 800 are merelyexamples of components that may be used with the method 800, and thatother components may also be utilized in some embodiments.

FIG. 9 is a flowchart illustrating an example method 900 for a dashboardthat supports social productivity in accordance with variousembodiments. As shown, the method 900 can begin at step 902, where theevent module 602 may detect an event that occurred with respect to thedata content object. The event may be one resulting from an actionperformed on the data content object through the ASP system 104 at arequest of a first user at the client 102.

At step 904, the criterion module 604 may determine whether an attributeof the first event satisfies a criterion. To determine whether anattribute of the first event satisfies a criterion, the criterion module604 may first identify the criterion by which the attribute isevaluated. According to some embodiments, the criterion may beidentified according to a second user currently accessing the dashboardand reviewing the event cards being presented by the dashboard.Additionally, in some embodiments, the identification of the criterioncan be based on the preferences or user settings of the second user orthe user second user's past activities with respect to data contentobjects accessible through the ASP system 104.

If, at decision point 906, the attributed is determined to not satisfythe criterion, the method 900 proceeds to step 908. At step 908, theevent module 602 may detect a next event that occurred with respect tothe data content object or another data content object. After step 908,method 900 can return to step 904.

If, at decision point 906, the attributed is determined to satisfy thecriterion, the method 900 proceeds to step 910. At step 910, the eventnotification module 606 may provide a first card relating to the eventand configured to be presented to the second user at a second client. Atstep 912, the presentation module 608 may present the first event cardthrough a dashboard configured to present the second user with eventsrelating to other data content objects in conjunction with the firstevent card. As described herein, a card can comprise some or all of thecontextual information captured in association with an event, a commentsection configured to present or receive a comment in association withthe event, or a secondary action (e.g., call of action) configured to beperformed an operation with respect to the card at the request of theuser perceiving the card (e.g., the percipient user).

At step 914, the event notification module 606 may receive a request fora secondary action with respect to the first card and perform therequest accordingly. Some examples of secondary actions include,entering a comment in association with the first card (e.g., liking anevent, liking an existing comment, or replying to a an existingcomment); sharing the first card with another user, deferringpresentation of the first card (e.g., defer based on time, date, oranother event), and assigning a task associated with the event toanother user.

Though the steps of method 900 may be depicted and described in acertain order, those skilled in the art will appreciate that the orderin which the steps are performed may vary between embodiments.Additionally, those skilled in the art will appreciate that thecomponents described above with respect to the method 900 are merelyexamples of components that may be used with the method 900, and thatother components may also be utilized in some embodiments.

FIG. 10 is a flowchart illustrating an example method 1000 for capturingcontext information, from a virtualized application, that supportssocial productivity in accordance with various embodiments. Forillustrative purposes, the method 1000 is depicted as involving theclient (C₁) 302, the access server (ACS₁) 312, and the applicationserver (APS₁) 318. In accordance with some embodiments, the method 1000can be utilized by the ACS server 312 to gather activity regardingfiles, or other types of data content objects, being accessed by anapplication executing on the application server 318 on behalf of theclient 302.

At step 1002, the client 302 may request the access server 312 foraccess to a selected file. Where an application compatible the selectedfile is not already executing, the access server 312 may arrange for aninstantiation of an application the compatible with the selected file tobe invoked on the application server 318. Once an application compatiblewith the file is executing on the application server 318 (hereafter, theexecuting application), at step 1004, the access server 312 may instructthe executing application access (e.g., open) the selected file.

In response the instruction, step 1006, the execution application on theapplication server 318 may access (e.g., open) the selected file. Forsome embodiments, the selected file may be accessed from a cloud-basedstorage service accessible by the executing application via the accessserver 312.

Subsequent to accessing the selected file, at step 1008, the applicationserver 318 may provide the client 302 with access to the executingapplication. For some embodiments, the access by the client 302 to theexecuting application on the application server 318 may be facilitatedthrough the access server 312.

At step 1010, the client 302 may request the executing application onthe application server 318 to perform actions that result in change tothe selected file. For some embodiments, the request from the client 302to the executing application on the application server 318 may befacilitated through the access server 312.

At step 1012, the executing application on the application server 318may perform the actions, requested by the client 302, on the selectedfile. The executing application may further save the changes that resultin the selected file. The executing application may save the changes bysaving a changed version of the selected file locally and then uploadingthe change version of the select file to the cloud-based storage servicefrom which the selected file originated.

At step 1014, the executing application on the application server 318may provide the access server 312 with contextual information regardingthe changes to the selected file. The contextual information provided bythe executing application may comprise a listing of the changesimplemented to the selected file, the types of changes implemented,metadata resulting from the changes, and/or operational transformationinformation relating to the changes. In accordance with someembodiments, the contextual information may be provided to the accessserver 312 upon request of the access server 312. For some embodiments,the request may be facilitated by a function call compatible with theapplication server 318 and/or the executing application. The functioncall may be one from an application programming interface (API)compatible with the application server 318 and/or the executingapplication.

At step 1016, the access server 312 may capture the contextualinformation regarding the changes to selected file, which can includethe contextual information received from the executing application onthe application server 318. In accordance with some embodiments, theaccess server 312 may store and maintain the captured contextualinformation in a history buffer. The history buffer utilized may be oneexclusively used for contextual information collected with respect tothe selected file. Based on the contextual information captured, theaccess server 312 may cause an event card relating to the changes to bepresented in the workspaces and dashboards of those users associatedwith the selected file.

FIG. 11 is a flowchart illustrating an example method 1100 fortraversing to a position related to an event in accordance with variousembodiments. For illustrative purposes, the method 1100 is depicted asinvolving the client (C₁) 302, the access server (ACS₁) 312, and theapplication server (APS₁) 318. In accordance with some embodiments, themethod 1100 can be utilized by the ACS server 312 to traverse to aposition in files, or another type of data content object, beingaccessed by an application executing on the application server 318 onbehalf of the client 302. The positions in files can those relating toevents that have occurred with respect to those files.

At step 1102, the client 302 may request a listing of files availablefor access through the access server 312. At step 1104, the accessserver 312 may provide the listing of files requested. At step 1106, theclient 302 may request the access server 312 to provide a listing ofactivities for a file selected from the listing provided at step 1104.In response, at step 1108, the access server 312 may obtain a listing ofactivities, for the selected from, from the contextual informationstored in association with the selected file. As described herein, thecontextual information may be stored in a history buffer related to(e.g., dedicated to) the selected file.

Included in the listing of activities are positions in the content ofthe selected file relating to the listed activities. To ensure that thepositions of the activities are accurate and current, during step 1108,the access server 312 may also utilize an operational transformation(OT) engine configured to update the position information contained inthe listing of activities. According to some embodiments, the accessserver 312 facilitate this update, the access server 312 may fetch allactivities and changes relating to the selected file, and pass allactivities and changes to the OT engine. The OT engine may scan theactivities and changes passed and update changes according to the OTengine logic. Subsequently, the OT engine may return the updatedposition information to the access server 312. According to someembodiments, where the client 302 is requesting a listing of activitiesfor a certain section (e.g., page N) of the selected file rather thanfor the entirety of the selected file, the access server 312 may need tofilter and provide the listing of activities accordingly, particularlyafter the OT engine has updated the position information.

At step 1110, the access server 312 may provide the client 302 with thelisting of activities requested in relation to the selected file. Theprovided listing of activities can include, for example, information forpositions in the selected file where activity occurred, a listing ofchanges that occurred in the selected file, and visualization of thechanges that occurred in the selected file. For some embodiments, theposition information provided in the listing of activities may besimilar in function and/or structure to the references described herein.

At step 1112, based on the position information provided in the listingof activities, the client 302 may request the access server 312 totraverse to a position in the selected file relating to a selectactivity provided in the listing of activities. At step 1114, the accessserver 312 may respond by instruction the application executing onbehalf of the client 302 to access the selected file and traverse to theposition in the selected file.

FIG. 12 is a screenshot of an example interface 1200 for accessing adata content object that is a file and presenting context in accordancewith various embodiments. As shown, the interface 1200 comprises acontent pane 1202 for viewing content from the file. The access tocontent through content pane 1202 may be provided by an applicationremotely executing on behalf of a client (e.g., at the applicationserver 318) and accessing the file on behalf of a user. Additionally,the interface 1200 comprises a context configured to provide contextualinformation in relation to the file being accessed through the contentpane 1202. As shown, the interface 1200 may present various types ofevent cards and other notification that can provide the user withcontextual information as the content is accessed. In this way, variousembodiments can provide contextual information regarding a data contentobject while accessing content of the data content object. For someembodiments, the interface 1200 may be provided by a workspace while thefile is being accessed through the ASP system 104.

FIG. 13, like FIG. 12, presents a screenshot of the interface 1200accessing a data content object that is a file and presenting context inaccordance with various embodiments. In FIG. 13, the interface 1200 ispresenting a comment interface 1300, which may be configured receive andassociate a comment with a portion 1302 of content contained in the filecurrently being accessed in the content pane 1202. In some embodiments,entering a comment through the comment interface 1300 may result in acomment being created, maintained, and associated with the fileexternally to content of the file and/or externally to the applicationbeing used to access the file through the content pane 1202. The commentcreated by the comment interface 1300 may be one stored and maintainedby embodiments in the contextual information for the file being accessedthrough the content pane 1202.

FIG. 14 is a screenshot of an example interface 1400 for accessing adata content object that is a file and for delegating portions ofcontent of data content object in accordance with various embodiments.As shown, through the interface 1400, a user can select portions ofcontent being accessed through a content pane 1402. The user can thenselect to share various portions of the content in the content pane 1402with one or more users. In FIG. 14 the user chose three differentportions 1404, 1406, and 1408 of content in the file with threedifferent users 1410, 1412, and 1414. In accordance with someembodiments, the user may share the different portions 1404, 1406, and1408 in association with tasks relating to those portions. For example,the user may task each of users 1410, 1412, and 1414 with editing theirrespective, shared portions 1404, 1406, and 1408 of content.Additionally, for some embodiments, the user can utilize share differentportions of content of a file such that the users receiving the sharecan use different means of access (e.g., word processing application,web-based word processing application, instant messaging, etc.) whenaccessing their respective shared portion.

FIG. 15 is a screenshots of example interfaces 1500, 1502, and 1504 eachrespectively accessing portions 1404, 1406, and 1408 of content sharedby a user through the interface 1400 of FIG. 14. As shown, each of theinterfaces 1500, 1502, and 1504 is access its respective portion using adifferent means of access. For example, the user of interface 1500 isaccessing its shared portion 1404 through a word processing application.The user of interface 1502 is accessing its shared portion 1406 througha web-based e-mail account. The user of interface 1504 is access itsshared portion 1408 through a web-based word processing interface.According to some embodiments, when the users of interfaces 1500, 1502,and 1504 individual save and submit changes to their respective sharedportions, those changes will be integrated into and reflected by theoriginal content of the file being accessed through the interface 1400.

FIG. 16 is a screenshot of an example interface 1600 for accessing aspace in association with a data content object that is a file inaccordance with various embodiments. As shown, the interface 1600comprises a properties pane 1602 and an activity stream pane 1610 forthe file being accessed through the interface 1600. The properties pane1602 includes a section 1604 that provides general information regardingthe file, such as filename, file owner, time since last modified, sizeof the file, and a summary of the file. The section 1604 also includesoptions that permit the user to access and edit the file, and follow theevents relating to the file. In accordance with some embodiments, when auser selects to follow the file through interface 1600, events relatingto the file may begin appearing in the user's dashboard and/or in spacesaccessed by the user. The properties pane 1602 also includes a section1606 that lists the users having shared access to the file, and asection 1608 that lists tags currently associated with the file.

The activity stream pane 1610 may be configured to present events (e.g.,event cards) in relation to the file current being accessed throughspace represented by the interface 1600. As shown, the activity streampane 1610 is presenting comments in relation to the file. In accordancewith some embodiments, where references to data content objects arepresented in association with events, selecting any of those referencesmay result in the user traversing to the data content object andaccessing the data content object through a space or an applicationcapable of accessing the content of the reference data content object.

FIG. 17 is a screenshot of an example interface 1700 for accessing alisting of workspaces in accordance with various embodiments. As shown,the interface 1700 presents a listing of workspaces that a user canshare, delete, rename, or access from the interface 1700. In accordancewith some embodiments, selecting any one of the workspaces list canresult in the user being provided with an interface that accesses theselected workspace. More regarding such an interface is discussed withrespect to FIG. 19, which depicts an example interface for accessing aworkspace in accordance with various embodiments. For some embodiments,the interface 1700 can enable a user to quickly create a new workspaceorganizing and facilitating collaborative efforts with respect to one ormore data content objects (e.g., files). FIG. 18 provides a screenshotof an example interface 1800 for creating a new workspace, and providesa screenshot of an example interface 1802 for sharing an existingworkspace with another user.

FIG. 19 is a screenshot of an example interface 1900 for accessing aworkspace in accordance with various embodiments. As shown, theinterface 1900 comprises a properties pane 1902 and an activity streampane 1910 for the workspace being accessed through the interface 1900.The properties pane 1902 includes a section 1904 that provides generalinformation regarding the workspace, such workspace name, cumulativedata size of the data content objects associated with the workspace, thecreator of the workspace, and the date of creation. The properties pane1902 includes a section 1906 that lists tags associated with theworkspace, files (or other types of data content objects) associatedwith the workspace, users that last commented regarding the workspace,and users having shared access to the workspace. The properties pane1902 also includes a section 1908 that provides a user with an optionview conversations regarding the workspace, an option to invite otherusers to the workspace (e.g., associating other users with theworkspace), and an option to add other document to the workspace (e.g.,associating other data content objects with the workspace).

The activity stream pane 1910 may be configured to present events (e.g.,event cards) in relation to the workspace current being accessed throughspace represented by the interface 1900. Events relating to theworkspace can include events relating to the users and/or data contentobjects (e.g., files) associated with the workspace). In FIG. 19, theactivity stream pane 1910 is presenting a listing of events thatincludes: events 1914 relating to changes to files associated with theworkspace; an event 1916 relating to a paragraph of a file, associatedwith the workspace, being shared with multiple users; an event 1918relating to an audio comment being posted in association with theworkspace; an event 1920 regarding a comment being posted in associationwith the workspace; an event 1922 relating to a conversation (e.g.,e-mail or instance message) reply sent in association with theworkspace; and events 1924 regarding to comments created within a fileassociated with the workspace.

The user may add to the conversation by leaving a text, audio, or videomessage through field 1912 of the interface 1900. Additionally, asshown, the listing of events includes one or more references to accessother data content objects references in the events.

FIG. 20 is a screenshot of an example dashboard interface 2000 inaccordance with various embodiments. In accordance with someembodiments, the dashboard interface may be provided to a user inassociation with one or more workspaces that provide the dashboard withevent information. As shown, the dashboard interface 2000 identifies theuser 2002 currently accessing the dashboard. As described herein, one ormore criteria may determine the events of relevance to presented throughthe dashboard interface 2000. Additionally, the one or more criteriautilized in determining the relevance of events may be based on the usercurrently access the dashboard.

In FIG. 20, the dashboard interface 2000 comprises columns that canpresent events gathered from one or more workspaces in connection withone or more data content objects associated with those workspaces. Thedashboard interface 2000 presents a change column 2004, a message column2006, a task and reminder column 2008, and a shared document column2010. Those skilled in the art will appreciate that for someembodiments, the interface for a dashboard may include more or lesscolumns of than those presented in FIG. 20, and of varying types.

The change column 2004 may be configured to collect and present eventsrelating to changes that occurred in files (e.g., documents) relevant tothe user accessing the dashboard interface 2000. Examples of thresholdconditions that can determine relevance of files to the user caninclude: did the user recently create the data content object, did theuser recently change the data content object; has the user commented onthe data content object; has the user reviewed the content of the datacontent object; and has the user collaboratively worked with anotheruser that has changed or otherwise accessed the data content object.

The message column 2006 may be configured to collect and presentmessages sent in association with files or workspaces relevant to theuser accessing the dashboard interface 2000. For some embodiments, themessages present may include those sent through an internal messagessystem, or those sent through external communication means. Examples ofexternal communications means can include e-mail, instant chatmessaging, mobile text messaging, or messaging through a social network(e.g., Twitter®). An example of an internal messaging system can includeone where messaging is facilitated by referencing a message with anidentifier that uniquely identifies a user in the workspace and/ordashboard environment (e.g., using the @ symbol with a username)provided by the ASP system 104.

The task and reminder column 2008 may be configured to collect andpresent the user with tasks that have been assigned to the user througha workspace (or other type of space) provided by the ASP system 104. Thetask and reminder column 2008 may be further configured to collect andpresent the user with reminder relating to data content objects relevantto the user. According to some embodiments, any data content objectaccessible through a workspace can be associated with a task or areminder, and such tasks and reminders can be presented through the taskand reminder column 2008.

The shared document column 2010 may be configured to collect and presentdocuments shared with the user. Additionally, the shared document column2010 can present a variety of non-document data content objects sharedamongst users. A data content object presented in the shared documentcolumn 2010 may include one directly shared between users, or oneindirectly shared by way of the data content object's association to aworkspace that is shared between users.

For some embodiments, each column may provide event cards from an orderbased on relevance (e.g., most relevant to least relevant).Additionally, each column may provide a count indicating the number ofevent cards that need to be addressed by the user (e.g., by way of asecond action associated with an event card). By doing so, someembodiments can enable or encourage a user to be more productive bykeeping the count close to or at zero. As described herein, as asecondary action, a user may dismiss, defer, delete or accept an eventcard presented in the dashboard. In some embodiments, the eventspresented in each of the columns of the dashboard can be filteredaccording to user preferences (e.g., categories) or user providedkeywords.

FIG. 21 provides screenshots of example event cards 2100, 2102, 2104,and 2106 for an example dashboard in accordance with variousembodiments. The event card 2100 presents an event regarding file“BUDGET-FY13.docx” being opened by user “Abel Cunningham.” In additionto providing the time elapsed since the event, the event card 2100permits a user reviewing the event to post a comment in association withthe event.

The event card 2102 presents an event regarding “Abel Cunningham”sharing a file with four other users. In addition to providing the timeelapsed since the event, the event card 2102 permits a user reviewingthe event to post a comment in association with the event.

The event card 2104 presents an event regarding 4 users editing the“BUDGET-FY13.docx.” The event card 2104 also indicates that it is thetop event card on a stack of related event cards that have beencollapsed (e.g., due space limitations on the dashboard or userpreference). The stack of event card may be related based on theirassociation to a common data content object (e.g., file). The event card2104 may permit a user to expand some or all of the event cards (e.g.,See All) in the stack of the event cards. The event card 2106 presentsthe stack of event cards when the event card 2104 is expanded.

FIG. 22 is a block diagram of an exemplary digital device 2200. Thedigital device 2200 comprises a processor 2202, a memory system 2204, astorage system 2206, a communication network interface 2208, an I/Ointerface 2210, and a display interface 2212 communicatively coupled toa bus 2214. The processor 2202 is configured to execute executableinstructions (e.g., programs). In some embodiments, the processor 2202comprises circuitry or any processor capable of processing theexecutable instructions.

The memory system 2204 is any memory configured to store data. Someexamples of the memory system 2204 are storage devices, such as RAM orROM. The memory system 2204 can comprise the ram cache. In variousembodiments, data is stored within the memory system 2204. The datawithin the memory system 2204 may be cleared or ultimately transferredto the storage system 2206.

The storage system 2206 is any storage configured to retrieve and storedata. Some examples of the storage system 2206 are flash drives, harddrives, optical drives, and/or magnetic tape. In some embodiments, thedigital device 2200 includes a memory system 2204 in the form of RAM anda storage system 2206 in the form of flash data. Both the memory system2204 and the storage system 2206 comprise computer readable media whichmay store instructions or programs that are executable by a computerprocessor including the processor 2202.

The communication network interface (com. network interface) 2208 can becoupled to a network (e.g., network 324) via the link 2216. Thecommunication network interface 2208 may support communication over anEthernet connection, a serial connection, a parallel connection, or anATA connection, for example. The communication network interface 2208may also support wireless communication (e.g., 802.11 a/b/g/n, WiMax).It will be apparent to those skilled in the art that the communicationnetwork interface 2208 can support many wired and wireless standards.

The optional input/output (I/O) interface 2210 is any device thatreceives input from the user and output data. The optional displayinterface 2212 is any device that is configured to output graphics anddata to a display. In one example, the display interface 2212 is agraphics adapter.

It will be appreciated by those skilled in the art that the hardwareelements of the digital device 2200 are not limited to those depicted inFIG. 22. A digital device 2200 may comprise more or less hardwareelements than those depicted. Further, hardware elements may sharefunctionality and still be within various embodiments described herein.In one example, encoding and/or decoding may be performed by theprocessor 2202 and/or a co-processor located on a GPU (e.g., an NVIDA®GPU).

The above-described functions and components can be comprised ofinstructions that are stored on a storage medium such as a computerreadable medium. The instructions can be retrieved and executed by aprocessor. Some examples of instructions are software, program code, andfirmware. Some examples of storage medium are memory devices, tape,disks, integrated circuits, and servers. The instructions areoperational when executed by the processor to direct the processor tooperate in accord with some embodiments. Those skilled in the art arefamiliar with instructions, processor(s), and storage medium.

Various embodiments are described herein as examples. It will beapparent to those skilled in the art that various modifications may bemade and other embodiments can be used without departing from thebroader scope of the invention(s) presented herein. These and othervariations upon the exemplary embodiments are intended to be covered bythe present invention(s).

1. A method by a first client device, the method comprising: awaitingreceipt of one or more data-content-object share indications, the one ormore data-content-object share indications indicating that one or moredata content objects has been shared by a user at a second client devicewith a user of the first client device, the one or more data contentobjects being stored in one or more data stores; in response toreceiving a particular data-content-object share indication that aparticular data content object has been shared with the user of thefirst client device, generating a particular share notification directedto the user of the first client device; awaiting receipt of one or moredata-content-object edit indications, the one or moredata-content-object edit indications identifying one or more edits tothe particular data content object; in response to receiving aparticular data-content-object edit indication that identifies one ormore particular edits to the particular data content object with theuser of the first client device, generating a particular editnotification directed to the user of the first client device; andpresenting a dashboard on the first client device, the dashboarddedicated to the first user and providing a portal to the particulardata content object, the dashboard including a first section fordisplaying share notifications including the particular sharenotification directed to the user of the first client device, and thedashboard including a second section different that the first sectionfor displaying edit notifications including the particular editnotification directed to the user of the first client device.
 2. Themethod of claim 1, wherein the one or more data stores includes cloudstorage.
 3. The method of claim 1, wherein the one or more edits to theparticular data content object are performed by the user at the secondclient device.
 4. The method of claim 1, wherein the dashboard providesa link to the particular data content object.
 5. The method of claim 1,further comprising: awaiting receipt of one or more task indications,the one or more task indications requesting the user of the first clientdevice to perform one or more tasks; and in response to receiving aparticular task indication, generating a particular task notification;wherein the dashboard includes a third section different than the firstand second sections for displaying task notifications including theparticular task notification.
 6. The method of claim 1, furthercomprising awaiting receipt of one or more message indications, the oneor more message indications including one or more messages from thesecond user at the second client device; and in response to receiving aparticular message indication, generating a particular messagenotification; wherein the dashboard includes a third section differentthan the first and second sections for displaying message notificationsincluding the particular message notification.
 7. The method of claim 1,wherein the dashboard presents the notifications using cards, each cardreporting at least one notification.
 8. The method of claim 1, whereinthe dashboard includes a count section, the count section being fordisplaying a count of the number of notifications in each section. 9.The method of claim 1, wherein each dashboard enables filtering thenotifications according to one or more conditions.
 10. A systemcomprising: an event module configured to: await receipt of one or moredata-content-object share indications, the one or moredata-content-object share indications indicating that one or more datacontent objects has been shared by a user at a second client device witha user of the first client device, the one or more data content objectsbeing stored in one or more data stores, and await receipt of one ormore data-content-object edit indications, the one or moredata-content-object edit indications identifying one or more edits tothe particular data content object; an event notification moduleconfigured to: generate a particular share notification directed to theuser of the first client device in response to receiving a particulardata-content-object share indication that a particular data contentobject has been shared with the user of the first client device, andgenerate a particular edit notification directed to the user of thefirst client device in response to receiving a particulardata-content-object edit indication that identifies one or moreparticular edits to the particular data content object with the user ofthe first client device; and a presentation module configured to presenta dashboard on the first client device, the dashboard dedicated to thefirst user and providing a portal to the particular data content object,the dashboard including a first section for displaying sharenotifications including the particular share notification directed tothe user of the first client device, and the dashboard including asecond section different that the first section for displaying editnotifications including the particular edit notification directed to theuser of the first client device.
 11. The system of claim 10, wherein theone or more data stores includes cloud storage.
 12. The system of claim10, wherein the one or more edits to the particular data content objectare performed by the user at the second client device.
 13. The system ofclaim 10, wherein the dashboard provides a link to the particular datacontent object.
 14. The system of claim 10, awaiting receipt of one ormore task indications, the one or more task indications requesting theuser of the first client device to perform one or more tasks; and inresponse to receiving a particular task indication, generating aparticular task notification; wherein the dashboard includes a thirdsection different than the first and second sections for displaying tasknotifications including the particular task notification.
 15. The systemof claim 10, wherein the event module is further configured to awaitreceipt of one or more message indications, the one or more messageindications including one or more messages from the second user at thesecond client device, the event notification module is furtherconfigured to generate a particular message notification in response toreceiving a particular message indication, and the dashboard includes athird section different than the first and second sections fordisplaying message notifications including the particular messagenotification.
 16. The system of claim 10, wherein the dashboard presentsthe notifications using cards, each card reporting at least onenotification.
 17. The system of claim 10, wherein the dashboard includesa count section, the count section being for displaying a count of thenumber of notifications in each section.
 18. The system of claim 10,wherein each dashboard enables filtering the notifications according toone or more conditions.
 19. A system comprising: means for awaitingreceipt of one or more data-content-object share indications, the one ormore data-content-object share indications indicating that one or moredata content objects has been shared by a user at a second client devicewith a user of the first client device, the one or more data contentobjects being stored in one or more data stores; means for generating aparticular share notification directed to the user of the first clientdevice in response to receiving a particular data-content-object shareindication that a particular data content object has been shared withthe user of the first client device; means for awaiting receipt of oneor more data-content-object edit indications, the one or moredata-content-object edit indications identifying one or more edits tothe particular data content object; means for in response to receiving aparticular data-content-object edit indication that identifies one ormore particular edits to the particular data content object, generatinga particular edit notification directed to the user of the first clientdevice; and means for presenting a dashboard on the first client device,the dashboard dedicated to the first user and providing a portal to theparticular data content object, the dashboard including a first sectionfor displaying share notifications including the particular sharenotification directed to the user of the first client device, and thedashboard including a second section different that the first sectionfor displaying edit notifications including the particular editnotification directed to the user of the first client device.
 20. Anon-transitory computer-readable medium configured to store executableinstructions, the instructions being executable by a processor toperform a method, the method comprising: awaiting receipt of one or moredata-content-object share indications, the one or moredata-content-object share indications indicating that one or more datacontent objects has been shared by a user at a second client device witha user of the first client device, the one or more data content objectsbeing stored in one or more data stores; in response to receiving aparticular data-content-object share indication that a particular datacontent object has been shared with the user of the first client device,generating a particular share notification directed to the user of thefirst client device; awaiting receipt of one or more data-content-objectedit indications, the one or more data-content-object edit indicationsidentifying one or more edits to the particular data content object; inresponse to receiving a particular data-content-object edit indicationthat identifies one or more particular edits to the particular datacontent object with the user of the first client device, generating aparticular edit notification directed to the user of the first clientdevice; and presenting a dashboard on the first client device, thedashboard dedicated to the first user and providing a portal to theparticular data content object, the dashboard including a first sectionfor displaying share notifications including the particular sharenotification directed to the user of the first client device, and thedashboard including a second section different that the first sectionfor displaying edit notifications including the particular editnotification directed to the user of the first client device.